Triple
T35719578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lochnaw |
E1032433
|
entity |
| Predicate | hasHereditaryConnection |
P83897
|
FINISHED |
| Object | Sheriff of Wigtown |
—
|
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: Sheriff of Wigtown | Statement: [Lochnaw, hasHereditaryConnection, Sheriff of Wigtown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHereditaryConnection Context triple: [Lochnaw, hasHereditaryConnection, Sheriff of Wigtown]
-
A.
hasHeritageConnectionWith
chosen
Indicates a relationship where two entities are linked through shared, inherited, or culturally transmitted heritage or ancestry.
-
B.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
C.
hereditaryAssociation
Indicates a relationship in which a trait, condition, or characteristic is passed from ancestors to descendants through genetic inheritance.
-
D.
hereditaryInFamily
Indicates that a trait, condition, or characteristic is passed down through generations within the same family.
-
E.
hasHereditaryBasis
Indicates that a trait, condition, or characteristic is determined or influenced by genetic inheritance passed down through family lines.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 3, 2026, 4:05 p.m.