Triple
T31947252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Owen Moore |
E815684
|
entity |
| Predicate | primaryLocationInGame |
P206130
|
FINISHED |
| Object | Seattle |
E166067
|
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: Seattle | Statement: [Owen Moore, primaryLocationInGame, Seattle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLocationInGame Context triple: [Owen Moore, primaryLocationInGame, Seattle]
-
A.
headquartersLocationInGame
Indicates the in-game location where an organization’s main base or central headquarters is situated.
-
B.
gameLocation
Indicates the place or venue where a game or match takes place.
-
C.
notableGameLocation
Indicates that a particular place is recognized as a significant or prominent location within a game.
-
D.
Game6Location
Indicates the location where the sixth game in a series or sequence takes place.
-
E.
inGameLocationType
Indicates that an entity has a specific type or category of location within a game world (e.g., city, dungeon, region).
- F. None of above. chosen
Provenance (5 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e8a1ec580819096e264dfc9d540e3 |
completed | June 14, 2026, 11:01 a.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:07 a.m.