Triple
T6718318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirkpatrick family |
E153328
|
entity |
| Predicate | hereditaryConnection |
P6431
|
FINISHED |
| Object | lands of Closeburn |
—
|
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: lands of Closeburn | Statement: [Kirkpatrick family, hereditaryConnection, lands of Closeburn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hereditaryConnection Context triple: [Kirkpatrick family, hereditaryConnection, lands of Closeburn]
-
A.
hereditaryAssociation
Indicates a relationship in which a trait, condition, or characteristic is passed from ancestors to descendants through genetic inheritance.
-
B.
hereditaryInFamily
Indicates that a trait, condition, or characteristic is passed down through generations within the same family.
-
C.
associatedHeir
chosen
Indicates that one entity is designated or recognized as the heir connected to, or inheriting from, another entity.
-
D.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
E.
heritageLine
Indicates that one entity is a historical or traditional predecessor, lineage, or source from which the other entity derives or continues.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d12765a48190b485176dc2ffa0fa |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:07 p.m.