Triple
T3088363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock 'n' Roller Coaster Starring Aerosmith |
E64427
|
entity |
| Predicate | precededByAttractionOnSite |
P35613
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Rock 'n' Roller Coaster Starring Aerosmith, precededByAttractionOnSite, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededByAttractionOnSite Context triple: [Rock 'n' Roller Coaster Starring Aerosmith, precededByAttractionOnSite, none]
-
A.
previousAttraction
chosen
Indicates that one entity was formerly an attraction or point of interest associated with another entity in the past.
-
B.
heldBefore
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
-
C.
appearsBefore
Indicates that one entity occurs, is positioned, or is presented earlier in an ordered sequence than another entity.
-
D.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
E.
successorUseOfSite
Indicates that one use or function of a site directly follows and replaces a previous use of that same site in time.
- 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada209fd24819088d887de0a4158f4 |
completed | March 8, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69ad9ded78f881908be6fc0fb7c35764 |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:03 p.m.