Triple
T819290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Region |
E17716
|
entity |
| Predicate | hasGamesAt |
P20883
|
FINISHED |
| Object | predetermined neutral sites |
—
|
LITERAL 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: predetermined neutral sites | Statement: [West Region, hasGamesAt, predetermined neutral sites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGamesAt Context triple: [West Region, hasGamesAt, predetermined neutral sites]
-
A.
hasPlacementGames
Indicates that an entity is associated with one or more preliminary or qualifying games used to determine its ranking, tier, or initial placement.
-
B.
hasGameType
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
-
C.
playedWith
Indicates that one entity engaged in play or a playful activity together with another entity.
-
D.
previousGames
Indicates that one entity represents games that occurred earlier in time relative to another entity.
-
E.
hasEsport
Indicates that an entity is associated with or participates in a specific electronic sports (esports) activity or competition.
- 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab976094819086d676404d745750 |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa76a7808190ac7fd9ba1a4cebcb |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab9634948190b25ea1b2e34df87d |
completed | March 1, 2026, 9:11 p.m. |
Created at: March 1, 2026, 7:38 p.m.