Triple
T34973042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aerosmith singles chronology |
E1008592
|
entity |
| Predicate | chronologicallyOrderedBy |
P181504
|
FINISHED |
| Object | release date |
—
|
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: release date | Statement: [Aerosmith singles chronology, chronologicallyOrderedBy, release date]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicallyOrderedBy Context triple: [Aerosmith singles chronology, chronologicallyOrderedBy, release date]
-
A.
chronologicallyOrdered
Indicates that the related entities are arranged in the order in which they occur in time.
-
B.
chronologicallyOrders
Indicates that one entity arranges or sequences other entities according to their positions in time, from earlier to later.
-
C.
chronologicalOrderInList
Indicates that one item appears before another in the temporal sequence defined by a specific list or ordered collection.
-
D.
areOrderedBy
chosen
Indicates that a set of items is arranged or sequenced according to a specified criterion or ordering rule.
-
E.
chronologicallyAfter
Indicates that one event or state occurs later in time than 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: May 3, 2026, 4:01 p.m.