Triple
T3005810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lascelles family |
E81897
|
entity |
| Predicate | hasLineageType |
P42556
|
FINISHED |
| Object | patrilineal noble lineage |
—
|
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: patrilineal noble lineage | Statement: [Lascelles family, hasLineageType, patrilineal noble lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLineageType Context triple: [Lascelles family, hasLineageType, patrilineal noble lineage]
-
A.
hasLineageStructure
chosen
Indicates that an entity participates in or exhibits a hierarchical ancestry or lineage-based structural relationship to other entities.
-
B.
hasLeaderLineage
Indicates that an entity’s lineage or ancestry includes one or more individuals who have held a leadership role.
-
C.
hasTypeOfHeritage
Indicates that an entity is associated with a specific category or classification of heritage (such as cultural, natural, or historical heritage).
-
D.
hasTypeGenus
Indicates that one entity is the type genus that formally defines or represents the taxonomic group of the other entity.
-
E.
hasTrailType
Indicates that an entity (such as a trail or route) is associated with a specific type or category of trail.
- 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_69ad8b1c4de88190a83b7cefaa1f2842 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a15ad9c81908255003bdb38d603 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad96180eb08190a524c5f458d41382 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.