Triple
T32487058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Expo / Springfield area |
E830270
|
entity |
| Predicate | hasTypeOfRide |
P23016
|
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: [World Expo / Springfield area, hasTypeOfRide, motion simulator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfRide Context triple: [World Expo / Springfield area, hasTypeOfRide, motion simulator]
-
A.
containsRideType
chosen
Indicates that one entity includes or offers a specific type or category of ride as part of its available options.
-
B.
rideType
Indicates the specific category or mode of transportation involved in a ride (e.g., standard, shared, premium).
-
C.
riderType
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
-
D.
hasBusType
Indicates that one entity (typically a bus or bus service) is associated with or classified by a specific type or category of bus.
-
E.
hasRideCycle
Indicates that one entity is associated with, or participates in, a recurring sequence or cycle of rides or ride operations.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
Created at: May 1, 2026, 12:58 a.m.