Triple
T16225946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joker (roller coaster, Six Flags México) |
E393843
|
entity |
| Predicate | usesTrackMaterial |
P122237
|
FINISHED |
| Object | steel |
—
|
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: steel | Statement: [Joker (roller coaster, Six Flags México), usesTrackMaterial, steel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTrackMaterial Context triple: [Joker (roller coaster, Six Flags México), usesTrackMaterial, steel]
-
A.
usesMaterialBy
Indicates that one entity makes use of or employs a material that is provided, specified, or created by another entity.
-
B.
usesTrackage
Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by another entity.
-
C.
hasTrackSurface
Indicates that an entity (such as a track) possesses or is characterized by a particular type of surface.
-
D.
appliedToMaterial
Indicates that an action, process, or treatment is performed on or directed toward a specific material.
-
E.
matrixMaterial
Indicates that one material serves as the continuous matrix phase in which another component or reinforcement is embedded.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d25f8bc81909aa59b794a528db2 |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:03 a.m.