Triple
T36549597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Udûn |
E901222
|
entity |
| Predicate | gameMechanicContext |
P15207
|
FINISHED |
| Object | open-world exploration |
—
|
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: open-world exploration | Statement: [Udûn, gameMechanicContext, open-world exploration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameMechanicContext Context triple: [Udûn, gameMechanicContext, open-world exploration]
-
A.
gameplayMechanic
Indicates a relationship where one entity functions as a rule, system, or interactive feature that defines how another entity can be played or operated within a game.
-
B.
gameContext
chosen
Indicates the situational framework or environment in which a game’s actions, rules, and interactions take place.
-
C.
notableLevelMechanic
Indicates that an entity is recognized for its significant involvement in designing, implementing, or innovating game level mechanics.
-
D.
interactionMechanism
Indicates the process or means by which one entity affects, influences, or interacts with another.
-
E.
gameEngineUsage
Indicates that one entity (such as a project or product) uses or is built upon a particular game engine.
- F. None of above.
Provenance (3 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.