Triple
T31601737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Motors pavilion |
E806364
|
entity |
| Predicate | replacementAttraction |
P192717
|
FINISHED |
| Object | Test Track |
—
|
NE NERFINISHED |
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: Test Track | Statement: [General Motors pavilion, replacementAttraction, Test Track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacementAttraction Context triple: [General Motors pavilion, replacementAttraction, Test Track]
-
A.
previousAttraction
Indicates that one entity was formerly an attraction or point of interest associated with another entity in the past.
-
B.
replacedVenue
Indicates that one venue has taken the place of another as its successor location or site.
-
C.
relatedAttraction
Indicates that one attraction is associated with or connected to another attraction in some relevant way.
-
D.
rethemedAttraction
Indicates that an existing attraction has been changed in theme or concept at a specific time or event.
-
E.
ridesAttraction
Indicates that an entity participates in experiencing or using an attraction, such as going on a ride at a venue or amusement location.
- F. None of above. chosen
Provenance (4 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
| PDg | Predicate description generation | batch_69fd28379d2c8190903ba228ee1cc756 |
completed | May 8, 2026, 12:03 a.m. |
Created at: April 30, 2026, 10:33 p.m.