Triple
T30610156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palmer family |
E779155
|
entity |
| Predicate | isLineageOf |
P152701
|
FINISHED |
| Object | Earls of Selborne |
—
|
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: Earls of Selborne | Statement: [Palmer family, isLineageOf, Earls of Selborne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLineageOf Context triple: [Palmer family, isLineageOf, Earls of Selborne]
-
A.
sourceOfLineageFor
Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
-
B.
isLineageType
Indicates that one entity represents a type or category within the lineage or ancestral line of another entity.
-
C.
successorInLineage
Indicates that one entity is the next direct descendant or inheritor in a genealogical or hierarchical lineage from another entity.
-
D.
isCrossoverOf
Indicates that one entity is a crossover derived from, combining elements of, or intersecting the domains of the referenced entities.
-
E.
hasLineageConnectionTo
chosen
Indicates a genealogical or ancestral relationship exists between two entities, such as descent, shared ancestry, or familial lineage.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689b87220819084859503a4458c0d |
completed | May 2, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:26 p.m.