Triple
T35510197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capital Wasteland |
E1026267
|
entity |
| Predicate | primaryGameWorldOf |
P190569
|
FINISHED |
| Object | Fallout 3 |
E314119
|
NE 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: Fallout 3 | Statement: [Capital Wasteland, primaryGameWorldOf, Fallout 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryGameWorldOf Context triple: [Capital Wasteland, primaryGameWorldOf, Fallout 3]
-
A.
primaryGame
Indicates that one game is the main or most significant game associated with an entity (such as a person, team, or event) among possibly several games.
-
B.
homeGameWorld
Indicates that a game or match is being played in the home world or home venue associated with a particular team or participant.
-
C.
primaryGameType
Indicates the main category or type of game with which an entity is primarily associated.
-
D.
inGameWorld
chosen
Indicates that an entity exists or is located within the context or boundaries of a particular game world.
-
E.
notableGameWorld
Indicates that a game’s world or setting is particularly significant, distinguished, or noteworthy in some meaningful way.
- F. None of above.
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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a390d2b791c8190a30392adb5fd3335 |
completed | June 22, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.