Triple
T27554022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldarion and Erendis |
E695585
|
entity |
| Predicate | protagonistLaterTitle |
P22452
|
FINISHED |
| Object | King of Númenor |
—
|
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: King of Númenor | Statement: [Aldarion and Erendis, protagonistLaterTitle, King of Númenor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistLaterTitle Context triple: [Aldarion and Erendis, protagonistLaterTitle, King of Númenor]
-
A.
protagonistTitle
Indicates that one entity is the title or designation held by the main or central character (protagonist) of a work or narrative.
-
B.
protagonistAlsoKnownAs
Indicates that an entity serving as a protagonist is alternatively referred to by another name or alias.
-
C.
protagonistFullName
Indicates that the subject entity is the full, proper name (including given and family names) of the story’s main protagonist.
-
D.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
E.
laterTitleHolder
chosen
Indicates that one entity is a subsequent holder of a particular title or position previously held by 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f8e4ab88190bfe86343b948a401 |
completed | May 2, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:36 p.m.