Triple
T12759819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Chums of Chance |
E304959
|
entity |
| Predicate | operatesVehicle |
P7364
|
FINISHED |
| Object | Inconvenience |
—
|
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: Inconvenience | Statement: [The Chums of Chance, operatesVehicle, Inconvenience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesVehicle Context triple: [The Chums of Chance, operatesVehicle, Inconvenience]
-
A.
drives
chosen
Indicates that one entity operates and controls the movement of a vehicle or similar conveyance transporting themselves or others.
-
B.
throughCarsOperateWith
Indicates that vehicles operate or move through an area, system, or route in coordination or interaction with another specified element.
-
C.
mainVehicle
Indicates that one vehicle is the primary or most important vehicle associated with a given entity or context.
-
D.
drivesOn
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
-
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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8d3eb08190ae998df5cc6d9ba6 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:28 p.m.