Triple
T32206894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Half-elven |
E822694
|
entity |
| Predicate | relatedLineage |
P124948
|
FINISHED |
| Object | House of Bëor |
E901174
|
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: House of Bëor | Statement: [Half-elven, relatedLineage, House of Bëor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedLineage Context triple: [Half-elven, relatedLineage, House of Bëor]
-
A.
lineageRelatedTo
chosen
Indicates a relationship where two entities are connected through a line of descent or ancestry within the same lineage.
-
B.
sourceOfLineageFor
Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
-
C.
relationToMainline
Indicates how something is connected or related to a primary or main sequence, path, or version.
-
D.
importantLineage
Indicates that one entity’s ancestry, heritage, or familial line is considered especially significant or influential in relation to another entity or context.
-
E.
genealogicalLine
Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
- 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_69f349093174819086e633c190a51aa8 |
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_6a2f3b9639b88190815b70d0944347d7 |
completed | June 14, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:36 a.m.