Triple
T32096160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eärendil |
E819726
|
entity |
| Predicate | choseKindredOf |
P173551
|
FINISHED |
| Object | Elves |
—
|
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: Elves | Statement: [Eärendil, choseKindredOf, Elves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: choseKindredOf Context triple: [Eärendil, choseKindredOf, Elves]
-
A.
usesKinshipSystem
Indicates that one entity organizes or interprets familial relationships according to the kinship classification system associated with another entity.
-
B.
kinshipGroupOf
Indicates that one entity is the kinship group or family group to which the other entity belongs.
-
C.
chosenGoddess
Indicates that a particular goddess has been selected or designated, typically as a preferred, patron, or special deity in relation to an entity.
-
D.
associatedHeir
Indicates that one entity is designated or recognized as the heir connected to, or inheriting from, another entity.
-
E.
intendedFamily
Indicates that one entity is planned or designated to be part of another entity’s family or familial group in the future.
- 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_69f6b64194148190ad2f84e111f66de0 |
completed | May 3, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:26 a.m.