Triple
T33624677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Eärendil |
E861369
|
entity |
| Predicate | unitesLineages |
P101267
|
FINISHED |
| Object | House of Hador |
—
|
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: House of Hador | Statement: [House of Eärendil, unitesLineages, House of Hador]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitesLineages Context triple: [House of Eärendil, unitesLineages, House of Hador]
-
A.
unites
Indicates that one entity brings together multiple entities into a single, cohesive whole or shared state.
-
B.
dynasticUnion
Indicates a political relationship in which two or more distinct states are ruled by the same dynasty or monarch while formally remaining separate entities.
-
C.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
D.
lineageSystem
Indicates a hierarchical ancestry or descent relationship that traces how entities are derived from or originate through one another within a system.
-
E.
ancestralLinks
chosen
Indicates a genealogical relationship where one entity is an ancestor of, or connected through a line of descent to, another entity.
- 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_69f34980fabc81909819228729a9ca84 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f822a0248190bf85849636eaff6d |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:41 a.m.