Triple
T26602755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal New Brunswick Regiment |
E667679
|
entity |
| Predicate | hasMilitiaOrigin |
P140800
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: true | Statement: [Royal New Brunswick Regiment, hasMilitiaOrigin, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitiaOrigin Context triple: [Royal New Brunswick Regiment, hasMilitiaOrigin, true]
-
A.
typeOfMilitia
chosen
Indicates the specific kind or category of militia to which an entity belongs or is classified.
-
B.
hasFactionalOrigin
Indicates that something originates from, or is derived from, a particular faction or internal subgroup.
-
C.
militaryOrigin
Indicates that an entity originates from, was created by, or is derived from a military organization, context, or background.
-
D.
derivedFromMilitaryOrCivil
Indicates that something originates from, is based on, or is obtained through military or civil (non-military governmental) sources, activities, or contexts.
-
E.
hasMilitaryAssociation
Indicates a relationship in which an entity is connected or affiliated with a military organization, activity, or function.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, 2:13 a.m.