Triple
T32171048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noldor |
E821708
|
entity |
| Predicate | firstHighKing |
P3535
|
FINISHED |
| Object | Finwë |
E848462
|
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: Finwë | Statement: [Noldor, firstHighKing, Finwë]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHighKing Context triple: [Noldor, firstHighKing, Finwë]
-
A.
firstMonarch
chosen
Indicates that the subject is the first monarch (initial ruler) of the object polity or domain.
-
B.
earliestWellAttestedKing
Indicates that the subject is recognized as the earliest historically well-documented king of the referenced polity or lineage.
-
C.
firstKnownLord
Indicates that the subject is the earliest historically or canonically recorded lord associated with the object.
-
D.
thirdMonarch
Indicates that the subject is the third monarch in a succession or lineage relative to a specified realm or dynasty.
-
E.
mostPowerfulKing
Indicates that the subject is the king who holds the greatest power or authority among a specified group of kings.
- 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3595856ed08190a460408bf5378450 |
completed | June 19, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:33 a.m.