Triple
T28933103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnegie family of Angus |
E733839
|
entity |
| Predicate | hasClanOrFamilyTies |
P7844
|
FINISHED |
| Object | Scottish Lowland families |
—
|
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: Scottish Lowland families | Statement: [Carnegie family of Angus, hasClanOrFamilyTies, Scottish Lowland families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClanOrFamilyTies Context triple: [Carnegie family of Angus, hasClanOrFamilyTies, Scottish Lowland families]
-
A.
hasFamilialTieTo
chosen
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
B.
hasClanChiefFamily
Indicates that an entity belongs to or is associated with the family of a clan chief.
-
C.
associatedClan
Indicates a relationship where an entity is linked or belongs to a particular clan, group, or lineage.
-
D.
hasRelatedTribe
Indicates that one tribe is associated or connected to another tribe in some relevant way, such as by kinship, alliance, or shared characteristics.
-
E.
hasHeritageConnectionWith
Indicates a relationship where two entities are linked through shared, inherited, or culturally transmitted heritage or ancestry.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 28, 2026, 8:29 a.m.