Triple
T28255111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan Chattan |
E712422
|
entity |
| Predicate | hasChiefClan |
P180314
|
FINISHED |
| Object | Clan Mackintosh |
—
|
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: Clan Mackintosh | Statement: [Clan Chattan, hasChiefClan, Clan Mackintosh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChiefClan Context triple: [Clan Chattan, hasChiefClan, Clan Mackintosh]
-
A.
hasClanChiefFamily
Indicates that an entity belongs to or is associated with the family of a clan chief.
-
B.
parentClanChief
Indicates that one entity serves as the clan chief of the parent clan of another entity.
-
C.
clanChiefBranchOf
Indicates that a particular clan chief belongs to, or is a leading figure within, a specific branch or subdivision of a larger clan.
-
D.
isSeatOfInfluentialClan
Indicates that a location serves as the primary base or stronghold of a powerful or influential clan.
-
E.
associatedClanChief
Indicates a relationship where an entity is linked or connected to a particular clan chief, typically as the chief responsible for or representing that entity.
- F. None of above. chosen
Provenance (4 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_69efb5207eb08190827e4c34048030b1 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
| PDg | Predicate description generation | batch_69f73adfd9a081908adae6bd59dfefb9 |
completed | May 3, 2026, 12:09 p.m. |
Created at: April 27, 2026, 11:07 p.m.