Triple
T37507150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Door of Shadows |
E932123
|
entity |
| Predicate | requiresChoice |
P106530
|
FINISHED |
| Object | joining the Venthyr Covenant |
—
|
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: joining the Venthyr Covenant | Statement: [Door of Shadows, requiresChoice, joining the Venthyr Covenant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresChoice Context triple: [Door of Shadows, requiresChoice, joining the Venthyr Covenant]
-
A.
requiresChoiceBetween
Indicates that one must select between two or more specified options, and that making such a choice is necessary in the given context.
-
B.
requiresDecision
chosen
Indicates that a choice or judgment must be made regarding the associated entities or situation.
-
C.
requiresPriorSelectionBy
Indicates that one option or entity can only be chosen or activated if another specified option or entity has already been selected beforehand.
-
D.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
E.
canChoose
Indicates that an entity has the ability or permission to select one option or entity from among alternatives.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0062e6bd788190a7b4f3e5befb5cbb |
completed | May 10, 2026, 10:50 a.m. |
| PD | Predicate disambiguation | batch_6a0061989d188190b4815b2de3e8676f |
completed | May 10, 2026, 10:44 a.m. |
Created at: May 3, 2026, 4:17 p.m.