Triple
T38586370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proudmoore |
E932354
|
entity |
| Predicate | foundedInFictionalUniverse |
P97495
|
FINISHED |
| Object | Kul Tiras |
—
|
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: Kul Tiras | Statement: [Proudmoore, foundedInFictionalUniverse, Kul Tiras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedInFictionalUniverse Context triple: [Proudmoore, foundedInFictionalUniverse, Kul Tiras]
-
A.
foundedByFictional
chosen
Indicates that an entity (such as an organization, place, or group) was established or created by a fictional character or entity.
-
B.
foundedInFictionalYear
Indicates that an entity was established or created in a year that exists only within a fictional or imaginary timeline, rather than in real-world history.
-
C.
hasFictionalUniverseStatus
Indicates that an entity holds a particular status or classification within a fictional universe or continuity.
-
D.
raisedInFictionalUniverse
Indicates that an entity was brought up or grew to maturity within a specified fictional universe or setting.
-
E.
isSetInFictionalUniverse
Indicates that a narrative work takes place within a specific fictional universe or setting.
- 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_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
Created at: May 3, 2026, 4:32 p.m.