Triple
T35010775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Courier Six |
E1009933
|
entity |
| Predicate | playerCharacterOf |
P167070
|
FINISHED |
| Object | Fallout: New Vegas |
—
|
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: Fallout: New Vegas | Statement: [Courier Six, playerCharacterOf, Fallout: New Vegas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerCharacterOf Context triple: [Courier Six, playerCharacterOf, Fallout: New Vegas]
-
A.
exampleCharacter
Indicates that one entity is an illustrative or sample character associated with another entity, typically used for demonstration or example purposes.
-
B.
mainCharacterField
chosen
Indicates that one entity is designated as the primary or central character associated with another entity, such as a work or narrative.
-
C.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
D.
cycleMainCharacter
Indicates that an entity serves as the primary or central character within a particular cycle, sequence, or recurring narrative.
-
E.
laterMainCharacterOf
Indicates that one entity becomes the main character of a work at a later point in time, succeeding another main character.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 3, 2026, 4:01 p.m.