Triple
T31954871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Reed of Allermuir |
E815875
|
entity |
| Predicate | holderPositionStart |
P173486
|
FINISHED |
| Object | 2020-01-13 |
—
|
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: 2020-01-13 | Statement: [Baron Reed of Allermuir, holderPositionStart, 2020-01-13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderPositionStart Context triple: [Baron Reed of Allermuir, holderPositionStart, 2020-01-13]
-
A.
honoreePositionStart
Indicates the point in time when an entity begins serving in the role or position for which it is being honored.
-
B.
titleHolderStartPosition
Indicates the position in a sequence or ranking at which an entity begins holding a particular title.
-
C.
currentHolderStart
Indicates the point in time when an entity’s current holder or possessor first began holding it.
-
D.
positionStartFor
Indicates the starting position or initial point at which an entity, event, or interval begins relative to another reference.
-
E.
initiatingPosition
Indicates the starting location or initial spatial position from which an action, process, or movement begins.
- F. None of above. chosen
Provenance (4 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:08 a.m.