Triple
T37471738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirna Noch |
E931169
|
entity |
| Predicate | inGameZoneType |
P183186
|
FINISHED |
| Object | subzone |
—
|
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: subzone | Statement: [Tirna Noch, inGameZoneType, subzone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inGameZoneType Context triple: [Tirna Noch, inGameZoneType, subzone]
-
A.
inGameZone
Indicates that an entity is located within a defined game zone or area of the game world.
-
B.
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).
-
C.
gameZoneType
chosen
Indicates the classification or category of a game zone within a game environment (e.g., safe area, combat zone, tutorial area).
-
D.
zoneNumberInGame
Indicates that an entity is associated with a specific numbered zone within a game.
-
E.
ballGameType
Indicates the specific kind or category of ball game associated with an event or activity.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.