Triple
T32650060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hairpin Turns |
E834704
|
entity |
| Predicate | isChronologicallyIn |
P137723
|
FINISHED |
| Object | The National discography |
—
|
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: The National discography | Statement: [Hairpin Turns, isChronologicallyIn, The National discography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isChronologicallyIn Context triple: [Hairpin Turns, isChronologicallyIn, The National discography]
-
A.
chronologicallyOrdered
Indicates that the related entities are arranged in the order in which they occur in time.
-
B.
chronologicallyAfter
Indicates that one event or state occurs later in time than another.
-
C.
hasChronologyRelation
Indicates a temporal ordering relationship between entities, specifying how one relates to another in time (e.g., before, after, or overlapping).
-
D.
chronologicallyBetween
Indicates that one event or time point occurs after a first reference point and before a second reference point in temporal order.
-
E.
chronologicallySetIn
chosen
Indicates that one event, scene, or narrative is situated at a specific point or period in time relative to a broader temporal context.
- 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_69f3492e773c81908afc10651e46cad3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c775d6188190b236fc4f89a11b61 |
completed | May 3, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:08 a.m.