Triple
T35511396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jehanna |
E1026292
|
entity |
| Predicate | inGameRepresentation |
P100146
|
FINISHED |
| Object | Daggerfall map location |
—
|
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: Daggerfall map location | Statement: [Jehanna, inGameRepresentation, Daggerfall map location]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inGameRepresentation Context triple: [Jehanna, inGameRepresentation, Daggerfall map location]
-
A.
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).
-
B.
inGameZone
chosen
Indicates that an entity is located within a defined game zone or area of the game world.
-
C.
inGameBehavior
Indicates how an entity acts, responds, or conducts itself within the context of a game or gameplay scenario.
-
D.
inGameName
Indicates that one entity is the name used by another entity within a specific game context.
-
E.
playsInGame
Indicates that an entity participates as a player in a particular game or match.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:04 p.m.