Triple
T32206738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herald of Gil-galad |
E822691
|
entity |
| Predicate | holderParentage |
P75214
|
FINISHED |
| Object | son of Eärendil and Elwing |
—
|
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: son of Eärendil and Elwing | Statement: [Herald of Gil-galad, holderParentage, son of Eärendil and Elwing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderParentage Context triple: [Herald of Gil-galad, holderParentage, son of Eärendil and Elwing]
-
A.
parentageIncludes
Indicates that a given parentage or lineage set contains or encompasses a particular parent or ancestral relationship.
-
B.
parentRelationship
chosen
Indicates a familial relationship in which one entity is the parent of another entity.
-
C.
heldByFamilyUntil
Indicates that something remained in the possession or care of a family up to a specified point in time.
-
D.
hasOwnerFatherOf
Indicates that the owner of an entity is the father of another specified entity.
-
E.
associatedWithPatriarch
Indicates that an entity has a relationship, connection, or affiliation with a patriarch, such as being under their authority, influence, or domain.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 12:36 a.m.