Triple
T35011472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dwemer |
E1009947
|
entity |
| Predicate | disappearanceEvent |
P47888
|
FINISHED |
| Object | Battle of Red Mountain |
—
|
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: Battle of Red Mountain | Statement: [Dwemer, disappearanceEvent, Battle of Red Mountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disappearanceEvent Context triple: [Dwemer, disappearanceEvent, Battle of Red Mountain]
-
A.
disappearanceOf
Indicates that one entity ceases to exist, be present, or be observable in relation to another entity, context, or time.
-
B.
disappearance
Indicates that an entity ceases to be present, visible, or detectable in a given context or location.
-
C.
disappearanceContext
Indicates the circumstances, conditions, or situational background under which a disappearance occurs or is reported.
-
D.
disappearanceCause
Indicates the reason or factor that led to an entity’s disappearance.
-
E.
disappearedDuring
chosen
Indicates that an entity ceased to be observable or present during the time span or event associated with another entity.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.