Triple
T38588207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruins of Lordaeron |
E932392
|
entity |
| Predicate | previousFactionControl |
P195109
|
FINISHED |
| Object | Kingdom of Lordaeron |
—
|
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: Kingdom of Lordaeron | Statement: [Ruins of Lordaeron, previousFactionControl, Kingdom of Lordaeron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousFactionControl Context triple: [Ruins of Lordaeron, previousFactionControl, Kingdom of Lordaeron]
-
A.
predecessorFaction
Indicates that one faction historically preceded and was replaced or succeeded by another faction.
-
B.
previousGarrison
Indicates that one entity served as the earlier or former garrison location or stationed force for another entity.
-
C.
precededByInTerritorialControl
chosen
Indicates that one entity previously held territorial control over an area that was later controlled by another specified entity.
-
D.
previousGarrisonName
Indicates that an entity previously had a different garrison name, specifying what that earlier name was.
-
E.
previousRegime
Indicates that one regime held power or authority immediately before another specified regime.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00119d821c8190874786391b27ef23 |
completed | May 10, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a001143fb6881909ac0ae8bfea04351 |
completed | May 10, 2026, 5:01 a.m. |
Created at: May 3, 2026, 4:32 p.m.