Triple
T5404507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carowinds |
E120857
|
entity |
| Predicate | Fury 325TopSpeed |
P63792
|
FINISHED |
| Object | approximately 95 mph |
—
|
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: approximately 95 mph | Statement: [Carowinds, Fury 325TopSpeed, approximately 95 mph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Fury 325TopSpeed Context triple: [Carowinds, Fury 325TopSpeed, approximately 95 mph]
-
A.
gForce
Indicates the gravitational or inertial acceleration experienced by an object, typically expressed as a multiple of standard gravity.
-
B.
Tornado ADV
Indicates that the action or event occurs in the manner of, or under conditions characterized by, a tornado (e.g., violently, turbulently, or with tornado-like intensity).
-
C.
fleetIncludes
Indicates that a particular fleet contains or is composed of the specified entity or entities as its members.
-
D.
acceleration0To60mph
Indicates the rate or time it takes for something to increase its speed from 0 to 60 miles per hour.
-
E.
drivingForce
Indicates a causal influence or motivating factor that propels or significantly shapes another process, event, or outcome.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8932b8bc8190bd31e11b167a7212 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd84660ea08190a641084814fcf94d |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd8931302c81908afcb0f011e91f09 |
completed | March 20, 2026, 5:51 p.m. |
Created at: March 20, 2026, 2:05 p.m.