Triple
T5307167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sci-Fi City |
E120129
|
entity |
| Predicate | hasRideTechnology |
P23569
|
FINISHED |
| Object | motion simulator |
—
|
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: motion simulator | Statement: [Sci-Fi City, hasRideTechnology, motion simulator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRideTechnology Context triple: [Sci-Fi City, hasRideTechnology, motion simulator]
-
A.
hasNavigationTechnology
Indicates that an entity is equipped with or utilizes a system or technology for determining or guiding its position, route, or movement.
-
B.
hasRideSystem
chosen
Indicates that one entity (typically an attraction or ride) uses or is associated with a particular ride system or ride mechanism.
-
C.
supportsDrivetrainFeature
Indicates that an entity provides or is compatible with a specified drivetrain-related capability or function.
-
D.
hasTransportationSystem
Indicates that an entity possesses, operates, or is served by an organized system for transporting people or goods.
-
E.
hasParkFeature
Indicates that a park includes, contains, or is associated with a specific feature or amenity.
- 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_69bd44704be88190acdb2ac481b0ff55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84534f9c8190bc19d4812060768d |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:53 p.m.