Triple
T28375419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luigi's Rollickin' Roadsters |
E718742
|
entity |
| Predicate | rideSystemTechnology |
P23569
|
FINISHED |
| Object | local positioning system |
—
|
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: local positioning system | Statement: [Luigi's Rollickin' Roadsters, rideSystemTechnology, local positioning system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rideSystemTechnology Context triple: [Luigi's Rollickin' Roadsters, rideSystemTechnology, local positioning system]
-
A.
rideSystem
Indicates that one entity uses or travels on a transportation system or service provided by another entity.
-
B.
rideFeature
Indicates that one entity is a feature, characteristic, or component associated with a particular ride.
-
C.
rideModel
Indicates that one entity is a specific model or type designation of a ride associated with another entity.
-
D.
transportTechnology
Indicates a relationship where one entity serves as the means, system, or method used to transport or move another entity from one place to another.
-
E.
hasRideSystem
chosen
Indicates that one entity (typically an attraction or ride) uses or is associated with a particular ride system or ride mechanism.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64c5e2f8c81909622f2f7e2093295 |
completed | May 2, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:02 a.m.