Triple
T6011460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gettin' Down at the Ampitheater |
E133841
|
entity |
| Predicate | followedByInChronology |
P6880
|
FINISHED |
| Object | tracks following it on One Day It'll All Make Sense |
—
|
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: tracks following it on One Day It'll All Make Sense | Statement: [Gettin' Down at the Ampitheater, followedByInChronology, tracks following it on One Day It'll All Make Sense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByInChronology Context triple: [Gettin' Down at the Ampitheater, followedByInChronology, tracks following it on One Day It'll All Make Sense]
-
A.
followedByComponent
Indicates that one component directly succeeds another component in a defined sequence or order.
-
B.
chronologicallyAfter
chosen
Indicates that one event or state occurs later in time than another.
-
C.
followedByClass
Indicates that one class or type is immediately succeeded by another class or type in a defined sequence or ordering.
-
D.
cededTo
Indicates that control, ownership, or authority over something was formally transferred from one entity to another.
-
E.
followsBetween
Indicates that one entity comes after or succeeds another entity within a specified context or sequence.
- 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_69c0087361a48190905c6b55969852b8 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f5159bc8190a988293bbbb99d24 |
completed | March 22, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69c049e4daf4819099bf870dc700e0a2 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.