Triple
T20319758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Macdonald |
E492177
|
entity |
| Predicate | clanBadgeAssociation |
P92259
|
FINISHED |
| Object | Clan Donald crest badge |
—
|
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: Clan Donald crest badge | Statement: [Lord Macdonald, clanBadgeAssociation, Clan Donald crest badge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clanBadgeAssociation Context triple: [Lord Macdonald, clanBadgeAssociation, Clan Donald crest badge]
-
A.
clanCrestAssociatedWith
chosen
Indicates that a particular clan crest is symbolically or traditionally linked to a specific clan or family.
-
B.
clanAssociationType
Indicates the specific nature or role of an entity’s association or membership within a clan.
-
C.
associatedClan
Indicates a relationship where an entity is linked or belongs to a particular clan, group, or lineage.
-
D.
sharesClanBadgeWith
Indicates that two entities possess and display the same clan badge, signifying shared clan affiliation or membership.
-
E.
clanSystem
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778abd14819098a01fd32217fdde |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b23a0788190bf1853ef5b81823f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:20 a.m.