Triple
T34639945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melian the Maia |
E889527
|
entity |
| Predicate | kinshipByDescent |
P95347
|
FINISHED |
| Object | Elrond |
—
|
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: Elrond | Statement: [Melian the Maia, kinshipByDescent, Elrond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kinshipByDescent Context triple: [Melian the Maia, kinshipByDescent, Elrond]
-
A.
kinshipNetwork
Indicates a familial relationship structure connecting individuals through blood, marriage, or adoption within a broader family network.
-
B.
ofDescent
chosen
Indicates a genealogical or ancestral relationship, specifying that one entity descends from or originates from another.
-
C.
usesKinshipSystem
Indicates that one entity organizes or interprets familial relationships according to the kinship classification system associated with another entity.
-
D.
patriarchalLineage
Indicates a familial relationship where descent, inheritance, or identity is traced through the male line or father’s ancestry.
-
E.
kinshipGroupOf
Indicates that one entity is the kinship group or family group to which the other entity belongs.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:04 a.m.