Triple
T27354075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government No. 1 (Black Watch) tartan |
E685636
|
entity |
| Predicate | isRegimentalTartanOf |
P162220
|
FINISHED |
| Object | various Highland regiments |
—
|
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: various Highland regiments | Statement: [Government No. 1 (Black Watch) tartan, isRegimentalTartanOf, various Highland regiments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegimentalTartanOf Context triple: [Government No. 1 (Black Watch) tartan, isRegimentalTartanOf, various Highland regiments]
-
A.
isRegimentalTartanOf
chosen
Indicates that one tartan pattern is officially designated as the regimental tartan of a particular military regiment.
-
B.
principalTartanOf
Indicates that one entity is the officially recognized primary tartan associated with another entity, such as a clan, organization, or region.
-
C.
tartan
Indicates that something has a tartan pattern or is characterized by a tartan design.
-
D.
sharesClanTartanWith
Indicates that two entities belong to clans that use the same tartan pattern.
-
E.
regimentalColourSymbol
Indicates that something serves as the symbolic emblem or design used on a regiment’s official flag or standard.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 11:50 a.m.