Triple
T35421457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donut Ghost House |
E1023806
|
entity |
| Predicate | gameWorld |
P40428
|
FINISHED |
| Object | Dinosaur Land |
—
|
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: Dinosaur Land | Statement: [Donut Ghost House, gameWorld, Dinosaur Land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameWorld Context triple: [Donut Ghost House, gameWorld, Dinosaur Land]
-
A.
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).
-
B.
homeGameWorld
Indicates that a game or match is being played in the home world or home venue associated with a particular team or participant.
-
C.
worldType
chosen
Indicates the classification or category of world or environment that an entity is associated with.
-
D.
gameContext
Indicates the situational framework or environment in which a game’s actions, rules, and interactions take place.
-
E.
gameEngineWork
Indicates that an entity works on, contributes to, or is employed in the development or maintenance of a 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.