Triple
T37555289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theater of Pain arena grounds |
E933681
|
entity |
| Predicate | factionTerritory |
P192686
|
FINISHED |
| Object | Necrolord |
—
|
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: Necrolord | Statement: [Theater of Pain arena grounds, factionTerritory, Necrolord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionTerritory Context triple: [Theater of Pain arena grounds, factionTerritory, Necrolord]
-
A.
factionName
Indicates the specific name assigned to a faction with which an entity is associated.
-
B.
factionType
Indicates the classification or category of a faction within a broader system or context.
-
C.
factionBase
Indicates that a particular location serves as the primary base or headquarters for a given faction.
-
D.
mainTerritoryOfInfluence
Indicates the primary geographic area where an entity exerts the most significant control, impact, or influence.
-
E.
factionRealm
Indicates a relationship where a faction is associated with, based in, or operating within a particular realm or domain.
- 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_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
| PDg | Predicate description generation | batch_69fd231bdd108190900369e07c854e95 |
completed | May 7, 2026, 11:41 p.m. |
Created at: May 3, 2026, 4:17 p.m.