Triple
T35459674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Citadel of the Lich |
E1024878
|
entity |
| Predicate | isOftenEncounteredAs |
P177012
|
FINISHED |
| Object | final dungeon in a campaign |
—
|
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: final dungeon in a campaign | Statement: [The Citadel of the Lich, isOftenEncounteredAs, final dungeon in a campaign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenEncounteredAs Context triple: [The Citadel of the Lich, isOftenEncounteredAs, final dungeon in a campaign]
-
A.
isOftenPresentedBy
Indicates that one entity is frequently the agent, host, or medium through which another entity is shown, delivered, or made available.
-
B.
isOftenResultOf
Indicates that one situation, event, or condition frequently occurs as a consequence or outcome of another.
-
C.
frequentlySeen
chosen
Indicates that one entity is observed or encountered many times or on a regular basis in relation to another entity.
-
D.
isFrequentlyIncludedIn
Indicates that something is regularly or commonly contained or made part of something else.
-
E.
isOftenKeptAs
Indicates that one entity is commonly maintained, owned, or retained by another as a regular or typical practice.
- 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_69f76df92f108190817222e520e22268 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.