Triple
T32558861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Immortan Joe |
E832164
|
entity |
| Predicate | commandsVehicle |
P144304
|
FINISHED |
| Object | The Gigahorse |
—
|
NE NERFINISHED |
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: The Gigahorse | Statement: [Immortan Joe, commandsVehicle, The Gigahorse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandsVehicle Context triple: [Immortan Joe, commandsVehicle, The Gigahorse]
-
A.
controlVehicle
chosen
Indicates having the authority or ability to direct, operate, or manage the movement and functioning of a vehicle.
-
B.
vehicleBase
Indicates that one entity serves as the foundational or underlying base for a vehicle-related entity or system.
-
C.
mainVehicle
Indicates that one vehicle is the primary or most important vehicle associated with a given entity or context.
-
D.
vehicleFor
Indicates that one entity serves as the means of transportation or conveyance for another entity.
-
E.
applicationVehicle
Indicates a relationship where a particular vehicle is used, specified, or associated within the context of an application or application process.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 1, 2026, 1:03 a.m.