Triple
T36549595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Udûn |
E901222
|
entity |
| Predicate | primaryProtagonistOperatesIn |
P177165
|
FINISHED |
| Object | Talion |
E901215
|
NE 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: Talion | Statement: [Udûn, primaryProtagonistOperatesIn, Talion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryProtagonistOperatesIn Context triple: [Udûn, primaryProtagonistOperatesIn, Talion]
-
A.
protagonistCity
Indicates the city in which the main character or protagonist of a work is primarily based or associated.
-
B.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
C.
protagonistLocation
chosen
Indicates the location or setting where the story’s main protagonist is situated at a given time.
-
D.
protagonistEmployerLocation
Indicates the location where the protagonist’s employer is based or operates.
-
E.
protagonistWorksFor
Indicates that the protagonist is employed by or under the authority of another entity (such as a person, organization, or group).
- F. None of above.
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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3d178366808190b0363a997318a30d |
completed | June 25, 2026, 11:56 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.