Triple
T35013208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iliac Bay |
E1009985
|
entity |
| Predicate | hasInGameMap |
P18236
|
FINISHED |
| Object | The Elder Scrolls II: Daggerfall world map |
—
|
NE NERFINISHED |
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: The Elder Scrolls II: Daggerfall world map | Statement: [Iliac Bay, hasInGameMap, The Elder Scrolls II: Daggerfall world map]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInGameMap Context triple: [Iliac Bay, hasInGameMap, The Elder Scrolls II: Daggerfall world map]
-
A.
hasInGameSign
Indicates that an entity is represented or referenced by a sign or signage within a game environment.
-
B.
hasInGameService
Indicates that one entity provides or is associated with a service that is available or usable within a game environment.
-
C.
hasInGameCategory
Indicates that an in-game item, action, or entity belongs to a specific predefined category within the game’s classification system.
-
D.
isOnSystemMap
chosen
Indicates that an entity is currently displayed or represented on a particular system map.
-
E.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a004d0b46148190bcec4ea67acfe170 |
completed | May 10, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_6a004c92283081909f229c1720af155a |
completed | May 10, 2026, 9:14 a.m. |
Created at: May 3, 2026, 4:01 p.m.