Triple
T32096159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eärendil |
E819726
|
entity |
| Predicate | grantedChoiceOfKindredTo |
P180902
|
FINISHED |
| Object | Half-elven |
—
|
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: Half-elven | Statement: [Eärendil, grantedChoiceOfKindredTo, Half-elven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedChoiceOfKindredTo Context triple: [Eärendil, grantedChoiceOfKindredTo, Half-elven]
-
A.
choseKindredOf
Indicates that one entity selected or designated another entity as a kindred, ally, or closely affiliated counterpart.
-
B.
agreedHeir
Indicates that one entity has been formally designated and accepted as the heir of another, typically through mutual agreement or legal arrangement.
-
C.
grantedBoonTo
Indicates that one entity has bestowed a favor, benefit, or special privilege upon another entity.
-
D.
madeHeirBy
Indicates that one entity is designated or appointed as the heir of another entity.
-
E.
adoptedAsHeir
Indicates that one entity has been formally chosen and accepted as the legal heir or successor of another entity.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
| PDg | Predicate description generation | batch_69f75788d40c819083bf2567b3091585 |
completed | May 3, 2026, 2:11 p.m. |
Created at: May 1, 2026, 12:26 a.m.