Triple
T35013169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bangkorai |
E1009984
|
entity |
| Predicate | zoneOrderInDaggerfallCovenant |
P165501
|
FINISHED |
| Object | third leveling zone |
—
|
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: third leveling zone | Statement: [Bangkorai, zoneOrderInDaggerfallCovenant, third leveling zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneOrderInDaggerfallCovenant Context triple: [Bangkorai, zoneOrderInDaggerfallCovenant, third leveling zone]
-
A.
zoneNumberInGame
chosen
Indicates that an entity is associated with a specific numbered zone within a game.
-
B.
zoneType
Indicates the classification or category of a zone that specifies its type or functional designation.
-
C.
zoneConcept
Indicates that one entity is associated with, defined by, or operates within a particular zone or conceptual area specified by another entity.
-
D.
zoneCount
Indicates the number of distinct zones associated with or contained within a given entity or context.
-
E.
zoneNumbering
Indicates a relationship where specific zones are assigned or associated with particular identifying numbers.
- 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_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.