Triple
T34797784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mages Guild |
E1003135
|
entity |
| Predicate | hasChapterIn |
P7252
|
FINISHED |
| Object | Morrowind |
—
|
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: Morrowind | Statement: [The Mages Guild, hasChapterIn, Morrowind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChapterIn Context triple: [The Mages Guild, hasChapterIn, Morrowind]
-
A.
containsChapter
Indicates that one entity (typically a larger work or document) includes another entity as a chapter within its structure.
-
B.
hadChapterOf
Indicates that an entity (such as a book or document) includes or contains a specific chapter as one of its parts.
-
C.
hasChapterStructure
Indicates that one entity is organized into chapters or contains a defined chapter-based structure in relation to another entity.
-
D.
hasGeneralChapter
Indicates that an entity is associated with, or contains, a general chapter (a broad or overarching section) within a larger structured document or framework.
-
E.
hasLocalChaptersIn
chosen
Indicates that an organization maintains one or more local chapters or branches within a specified geographic area or location.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
Created at: May 3, 2026, 3:59 p.m.