Triple
T37459965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Widow Faerlina |
E930892
|
entity |
| Predicate | encounterPosition |
P5131
|
FINISHED |
| Object | second boss of the Arachnid Quarter |
—
|
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: second boss of the Arachnid Quarter | Statement: [Grand Widow Faerlina, encounterPosition, second boss of the Arachnid Quarter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encounterPosition Context triple: [Grand Widow Faerlina, encounterPosition, second boss of the Arachnid Quarter]
-
A.
encounterLocation
Indicates the place or setting where two or more entities meet, interact, or come into contact.
-
B.
positionOften
Indicates that one entity frequently holds, occupies, or is located at a particular position relative to another entity or context.
-
C.
positionSought
Indicates the specific role, job, or position that an entity is aiming to obtain or apply for.
-
D.
positionEstablishedIn
Indicates the point in time or event when a particular position, role, or office was formally created or instituted.
-
E.
positionA
chosen
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.