Triple
T38585314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Horde |
E932332
|
entity |
| Predicate | foundedInTimeline |
P200277
|
FINISHED |
| Object | alternate Draenor timeline |
—
|
LITERAL FINISHED |
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: alternate Draenor timeline | Statement: [Iron Horde, foundedInTimeline, alternate Draenor timeline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedInTimeline Context triple: [Iron Horde, foundedInTimeline, alternate Draenor timeline]
-
A.
foundedInYearApprox
Indicates that an entity was established or came into existence around an approximate year, rather than on a precisely known date.
-
B.
foundedBefore
Indicates that one entity was established or created at an earlier time than the other entity.
-
C.
foundedAt
Indicates the time or date at which an entity (such as an organization, project, or institution) was established or created.
-
D.
foundedAfter
Indicates that one entity was founded at a later time than another entity.
-
E.
foundedOn
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
| PDg | Predicate description generation | batch_69ff7dce25d88190b167a014661bc4ba |
completed | May 9, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:32 p.m.