Triple
T14746922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super 8 Aqua Racer |
E346495
|
entity |
| Predicate | rideMedium |
P57710
|
FINISHED |
| Object | water |
—
|
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: water | Statement: [Super 8 Aqua Racer, rideMedium, water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rideMedium Context triple: [Super 8 Aqua Racer, rideMedium, water]
-
A.
rideType
Indicates the specific category or mode of transportation involved in a ride (e.g., standard, shared, premium).
-
B.
hasRideMedium
chosen
Indicates that an entity’s ride or journey is conducted using a particular transportation medium or mode.
-
C.
rideModel
Indicates that one entity is a specific model or type designation of a ride associated with another entity.
-
D.
rideStyle
Indicates the manner or characteristic way in which an entity rides or is ridden (e.g., in terms of technique, comfort, or behavior).
-
E.
riderType
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7d116e88190828b163b18d80f68 |
completed | April 14, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.