Triple
T1188697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wave Swinger |
E25305
|
entity |
| Predicate | hasRideMechanism |
P23569
|
FINISHED |
| Object | suspension chains |
—
|
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: suspension chains | Statement: [Wave Swinger, hasRideMechanism, suspension chains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRideMechanism Context triple: [Wave Swinger, hasRideMechanism, suspension chains]
-
A.
hasRideSystem
chosen
Indicates that one entity (typically an attraction or ride) uses or is associated with a particular ride system or ride mechanism.
-
B.
hasLocomotive
Indicates that one entity possesses or is equipped with a locomotive as part of its composition or operation.
-
C.
usesRollingStock
Indicates that one entity employs or operates specific rolling stock (such as rail vehicles) in its activities or services.
-
D.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
E.
hasCableCar
Indicates that one entity possesses, operates, or is served by a cable car system connecting it to other locations or points.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd568cf481908d10cf19a3ce28f3 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5bacc481909e8dfd5215e4711a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.