Triple
T18856040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Last Command |
E461171
|
entity |
| Predicate | timelinePlacement |
P89854
|
FINISHED |
| Object | 9 ABY |
—
|
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: 9 ABY | Statement: [The Last Command, timelinePlacement, 9 ABY]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timelinePlacement Context triple: [The Last Command, timelinePlacement, 9 ABY]
-
A.
datePlacement
Indicates a temporal relationship specifying when an event or entity is positioned or scheduled in time, such as the assigned or actual date of occurrence.
-
B.
timelineUse
Indicates that one entity utilizes or incorporates another entity within a temporal sequence or schedule (a timeline).
-
C.
timelineDetail
Indicates a detailed view or breakdown of events, actions, or states along a timeline associated with an entity or process.
-
D.
chronologicalPoint
chosen
Indicates that something is associated with, occurs at, or is anchored to a specific point in time within a chronological sequence.
-
E.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c05d0bb8819094d0447441f85b57 |
completed | April 20, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.