Triple
T1010692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Amazing Adventures of Spider-Man – The Ride 4K3D |
E21814
|
entity |
| Predicate | hasRideVehicleType |
P1776
|
FINISHED |
| Object | multi-row ride vehicle |
—
|
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: multi-row ride vehicle | Statement: [The Amazing Adventures of Spider-Man – The Ride 4K3D, hasRideVehicleType, multi-row ride vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRideVehicleType Context triple: [The Amazing Adventures of Spider-Man – The Ride 4K3D, hasRideVehicleType, multi-row ride vehicle]
-
A.
hasVehicle
Indicates that one entity possesses, owns, or is assigned a vehicle.
-
B.
vehicleType
chosen
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
C.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
D.
rideType
Indicates the specific category or mode of transportation involved in a ride (e.g., standard, shared, premium).
-
E.
vehicleUsed
Indicates that a particular vehicle is utilized or employed in performing an action, event, or activity.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7f4c66c8190b6098fb72c1465a3 |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b7203124819091de68cba5f731c1 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.