Triple
T37551294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azjol-Nerub |
E933595
|
entity |
| Predicate | partiallyConqueredBy |
P44010
|
FINISHED |
| Object | Lich King |
—
|
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: Lich King | Statement: [Azjol-Nerub, partiallyConqueredBy, Lich King]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyConqueredBy Context triple: [Azjol-Nerub, partiallyConqueredBy, Lich King]
-
A.
conqueredInPartBy
chosen
Indicates that one entity has gained control over a portion, but not the entirety, of another entity through conquest.
-
B.
conqueredIn
Indicates that one entity gained control over another entity or territory as a result of a specific conquest event or campaign.
-
C.
notConqueredBy
Indicates that one entity has not been taken over, subdued, or brought under the control of another entity.
-
D.
realmConqueredBy
Indicates that a particular realm or territory has been taken over and brought under the control of a specified conqueror.
-
E.
conqueredFrom
Indicates that one entity gained control of another entity by taking it from a third party that previously held it.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 3, 2026, 4:17 p.m.