Triple
T32599323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elladan |
E833319
|
entity |
| Predicate | choiceOfKindred |
P173551
|
FINISHED |
| Object | Elven-kind |
—
|
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: Elven-kind | Statement: [Elladan, choiceOfKindred, Elven-kind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: choiceOfKindred Context triple: [Elladan, choiceOfKindred, Elven-kind]
-
A.
choseKindredOf
chosen
Indicates that one entity selected or designated another entity as a kindred, ally, or closely affiliated counterpart.
-
B.
chosenGoddess
Indicates that a particular goddess has been selected or designated, typically as a preferred, patron, or special deity in relation to an entity.
-
C.
chosenFate
Indicates that an entity has actively selected or accepted a particular destiny or outcome, rather than having it imposed by external forces.
-
D.
sisterRace
Indicates that two races or species are closely related or derived from a common origin, often treated as parallel or counterpart groups.
-
E.
selectionRitual
Indicates a process or ceremony through which one or more entities are chosen from a set of candidates.
- 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c698588c819088e3bc33318651f3 |
completed | May 3, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:05 a.m.