Triple
T25826667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Stewart tartan |
E650548
|
entity |
| Predicate | clanOfOrigin |
P120138
|
FINISHED |
| Object | Clan Stewart |
—
|
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 Stewart | Statement: [Royal Stewart tartan, clanOfOrigin, Clan Stewart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clanOfOrigin Context triple: [Royal Stewart tartan, clanOfOrigin, Clan Stewart]
-
A.
clanFamilyOf
Indicates that one entity belongs to, descends from, or is otherwise affiliated with the same clan or extended family group as another entity.
-
B.
notableClanOrigin
chosen
Indicates that an entity is notably associated with originating from, belonging to, or being historically linked to a particular clan.
-
C.
clanNameOrigin
Indicates the source or basis from which a clan’s name is derived.
-
D.
clanType
Indicates the specific category or classification of a clan within a broader clan system or hierarchy.
-
E.
descendantClan
Indicates that one clan is a later-generation offshoot or subordinate lineage that originates from another clan.
- 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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f601954a68819083f749ed4b29a059 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:36 a.m.