Triple
T15379677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maclean of Ardgour |
E367765
|
entity |
| Predicate | usesClanSystemFeatures |
P15952
|
FINISHED |
| Object | tartan |
—
|
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: tartan | Statement: [Maclean of Ardgour, usesClanSystemFeatures, tartan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesClanSystemFeatures Context triple: [Maclean of Ardgour, usesClanSystemFeatures, tartan]
-
A.
hasClanStatus
Indicates that an entity holds a specific role, rank, or membership status within a clan or clan-like group.
-
B.
usesClanPraise
Indicates that one entity employs or invokes the traditional praise names or laudatory expressions associated with a particular clan in relation to another entity.
-
C.
clanSystem
chosen
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
-
D.
hasClanSeat
Indicates that an entity holds an official seat or position within a particular clan.
-
E.
isPrincipalClanOf
Indicates that one clan holds primary or leading status over another clan within a hierarchical or organizational structure.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e6044488190b0499db109f7f821 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.