Triple
T37470218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Necrolords |
E931133
|
entity |
| Predicate | zoneAssociation |
P2160
|
FINISHED |
| Object | House of the Chosen |
—
|
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: House of the Chosen | Statement: [Necrolords, zoneAssociation, House of the Chosen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneAssociation Context triple: [Necrolords, zoneAssociation, House of the Chosen]
-
A.
regionOfAssociation
Indicates a broader geographic or spatial area with which an entity is functionally, contextually, or organizationally associated.
-
B.
zoneStatus
Indicates the current operational or condition state assigned to a specific zone within a system or environment.
-
C.
zone
chosen
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
D.
zoneAuthority
Indicates that an entity has official control, responsibility, or decision-making power over a specific zone or area.
-
E.
zoneBased
Indicates that the relationship or action is determined or constrained by specific geographic or logical zones.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.