Triple
T35421634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donut Secret area lake |
E1023810
|
entity |
| Predicate | locatedInGameWorldRegion |
P40
|
FINISHED |
| Object | Donut Plains region |
E312402
|
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: Donut Plains region | Statement: [Donut Secret area lake, locatedInGameWorldRegion, Donut Plains region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInGameWorldRegion Context triple: [Donut Secret area lake, locatedInGameWorldRegion, Donut Plains region]
-
A.
regionInGame
Indicates that a specific region or area exists within or is part of a particular game.
-
B.
inGameLocationType
Indicates that an entity has a specific type or category of location within a game world (e.g., city, dungeon, region).
-
C.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
regionRuledLocatedIn
Indicates that the region governed or ruled by an entity is geographically located within a specified larger area or place.
-
E.
locatedInMetaregion
Indicates that one entity is geographically or administratively situated within a larger metaregion.
- 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_69f76df6704081909900c60be10d5849 |
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_6a385bbf67bc819091e37010fff710ad |
completed | June 21, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.