Triple
T37553398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valley of Spirits zeppelin tower |
E933639
|
entity |
| Predicate | inGamePerspective |
P189061
|
FINISHED |
| Object | 3D world object |
—
|
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: 3D world object | Statement: [Valley of Spirits zeppelin tower, inGamePerspective, 3D world object]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inGamePerspective Context triple: [Valley of Spirits zeppelin tower, inGamePerspective, 3D world object]
-
A.
inGameZone
Indicates that an entity is located within a defined game zone or area of the game world.
-
B.
inGameBehavior
Indicates how an entity acts, responds, or conducts itself within the context of a game or gameplay scenario.
-
C.
perspectiveOf
Indicates that something is expressed, depicted, or understood from the viewpoint or standpoint of a particular entity.
-
D.
inGameType
Indicates that an entity participates in or belongs to a specific type or category within a game (e.g., game mode, classification, or role).
-
E.
inGameStatus
Indicates the current state or condition of an entity within the context of a game (e.g., active, paused, eliminated).
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbb083ab708190a18b045311106f27 |
completed | May 6, 2026, 9:20 p.m. |
Created at: May 3, 2026, 4:17 p.m.