Triple
T32095706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanyar |
E819716
|
entity |
| Predicate | relatedKindred |
P7844
|
FINISHED |
| Object | Noldor |
E821708
|
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: Noldor | Statement: [Vanyar, relatedKindred, Noldor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedKindred Context triple: [Vanyar, relatedKindred, Noldor]
-
A.
closestLivingRelatives
Indicates that the related entities are the most closely related to each other among all currently living entities, in terms of evolutionary or genealogical proximity.
-
B.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
C.
siblingOrRelative
Indicates that two entities are related to each other by blood, marriage, or family ties, including but not limited to being siblings.
-
D.
coveredFamilyMember
Indicates that one person is included as an eligible dependent or beneficiary under another person’s insurance or benefit coverage.
-
E.
hasFamilialTieTo
chosen
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
- 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_69f34901106881908ea893ad504a08be |
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_6a2f46bb4b7c8190b506dbeb0a6c79b7 |
completed | June 15, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:26 a.m.