Triple
T37540184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake of Kalandra |
E933305
|
entity |
| Predicate | endgameIntegration |
P188225
|
FINISHED |
| Object | maps |
—
|
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: maps | Statement: [Lake of Kalandra, endgameIntegration, maps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endgameIntegration Context triple: [Lake of Kalandra, endgameIntegration, maps]
-
A.
endgameContentFor
Indicates that something serves as endgame content designed for a particular game, mode, or player progression stage.
-
B.
ElamEnding
Indicates that an entity marks the end or termination of something related to Elam (e.g., an Elam-related period, event, or process).
-
C.
gameEngine
Indicates that one entity serves as the game engine or core runtime system used to develop, run, or power another entity (such as a game or interactive application).
-
D.
gameEngineUsage
Indicates that one entity (such as a project or product) uses or is built upon a particular game engine.
-
E.
hasGameEndCondition
Indicates that an entity specifies the condition or set of conditions under which a game is considered finished or concluded.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba5ee00fc81909be7b947a3f95034 |
completed | May 6, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.