Triple
T37551592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pit of Saron |
E933601
|
entity |
| Predicate | entranceNPC |
P189058
|
FINISHED |
| Object | Archmage Lan'dalock |
—
|
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: Archmage Lan'dalock | Statement: [Pit of Saron, entranceNPC, Archmage Lan'dalock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entranceNPC Context triple: [Pit of Saron, entranceNPC, Archmage Lan'dalock]
-
A.
entranceTrait
Indicates a characteristic or feature associated with how an entity enters or is accessed (e.g., through a particular type or style of entrance).
-
B.
entranceGimmick
Indicates a distinctive feature, stunt, or presentation style used when someone or something makes an entrance.
-
C.
entranceFaction
Indicates a relationship where a specific faction controls, guards, or is otherwise associated with an entrance or access point.
-
D.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
E.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbb083ab708190a18b045311106f27 |
completed | May 6, 2026, 9:20 p.m. |
Created at: May 3, 2026, 4:17 p.m.