Triple
T26602969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 80th Regiment |
E667685
|
entity |
| Predicate | hasSuccessorUnit |
P157676
|
FINISHED |
| Object | The Royal Montreal Regiment |
—
|
NE NERFINISHED |
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: The Royal Montreal Regiment | Statement: [80th Regiment, hasSuccessorUnit, The Royal Montreal Regiment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuccessorUnit Context triple: [80th Regiment, hasSuccessorUnit, The Royal Montreal Regiment]
-
A.
hasSuccessorUsers
Indicates that one user or set of users is followed or replaced by another user or set of users in a sequence or succession.
-
B.
successorUnitIntegratedInto
Indicates that a subsequent or replacement unit has been incorporated into, or merged with, another unit as part of an organizational or structural succession.
-
C.
hasSuccessorSegment
Indicates that one segment directly follows another segment in a sequence or ordered structure.
-
D.
hasSuccessorShip
Indicates that one entity is the ship that follows or replaces another ship in a sequence or lineage.
-
E.
hasCurrentSuccessor
chosen
Indicates that one entity is the immediate next or following entity in a current, ordered sequence or progression of another entity.
- 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_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 27, 2026, 2:13 a.m.