Triple
T35010961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunset Sarsaparilla |
E1009937
|
entity |
| Predicate | headquartersLocationInGame |
P182480
|
FINISHED |
| Object | New Vegas region |
—
|
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: New Vegas region | Statement: [Sunset Sarsaparilla, headquartersLocationInGame, New Vegas region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headquartersLocationInGame Context triple: [Sunset Sarsaparilla, headquartersLocationInGame, New Vegas region]
-
A.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
B.
systemHeadquartersLocation
Indicates the location where an organization’s main administrative or central operations are based.
-
C.
headquartersAt
Indicates that an organization’s main administrative center or primary office is located at a specified place.
-
D.
campaignHeadquartersLocation
Indicates the specific place where a political or organizational campaign’s main headquarters is located.
-
E.
headquartersGrantedLocation
Indicates that a particular location has been officially designated or granted as the headquarters of an organization or entity.
- F. None of above. chosen
Provenance (4 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_69f78dbf72648190a4971a558e9d1889 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78ce43094819093857fc99f269afe |
completed | May 3, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:01 p.m.