Triple
T28899101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nemesis |
E732904
|
entity |
| Predicate | playerVehicle |
P61976
|
FINISHED |
| Object | Vic Viper |
—
|
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: Vic Viper | Statement: [Nemesis, playerVehicle, Vic Viper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerVehicle Context triple: [Nemesis, playerVehicle, Vic Viper]
-
A.
livesInVehicle
Indicates that an entity resides or habitually stays within a vehicle as its primary place of living or presence.
-
B.
mainVehicle
chosen
Indicates that one vehicle is the primary or most important vehicle associated with a given entity or context.
-
C.
parentVehicle
Indicates that one vehicle serves as the primary or containing vehicle from which another vehicle is derived, owned, or hierarchically related.
-
D.
controlVehicle
Indicates having the authority or ability to direct, operate, or manage the movement and functioning of a vehicle.
-
E.
hostVehicle
Indicates that one entity serves as the primary or reference vehicle in relation to another entity or context.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 28, 2026, 8:01 a.m.