Triple
T31439846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thousand-Year Door |
E802035
|
entity |
| Predicate | chamberLocatedIn |
P171877
|
FINISHED |
| Object | deepest level of Rogueport Sewers |
—
|
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: deepest level of Rogueport Sewers | Statement: [Thousand-Year Door, chamberLocatedIn, deepest level of Rogueport Sewers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chamberLocatedIn Context triple: [Thousand-Year Door, chamberLocatedIn, deepest level of Rogueport Sewers]
-
A.
chamber1
Indicates that an entity is a chamber or room, typically serving as an enclosed space within a larger structure.
-
B.
chamber2
Indicates that one entity serves as a secondary or inner chamber, room, or compartment associated with another entity.
-
C.
chamberType
Indicates the specific kind or category of chamber associated with an entity (e.g., room, compartment, or enclosed space type).
-
D.
chamberServed
Indicates that a particular legislative chamber was the one in which an individual held office or performed their official service.
-
E.
typeOfChamber
Indicates the specific kind or category of chamber that an entity belongs to or is classified as.
- F. None of above. chosen
Provenance (4 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a5f656ec81909e02b0b873303adf |
completed | May 3, 2026, 1:33 a.m. |
Created at: April 30, 2026, 9:04 p.m.