Triple
T35146722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunn Ancient |
E1014857
|
entity |
| Predicate | hasTartanCategory |
P10431
|
FINISHED |
| Object | clan 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: clan tartan | Statement: [Gunn Ancient, hasTartanCategory, clan tartan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTartanCategory Context triple: [Gunn Ancient, hasTartanCategory, clan tartan]
-
A.
tartan
chosen
Indicates that something has a tartan pattern or is characterized by a tartan design.
-
B.
sharesClanTartanWith
Indicates that two entities belong to clans that use the same tartan pattern.
-
C.
tartanStatus
Indicates the relationship between an entity and its classification or condition regarding tartan (e.g., whether a tartan pattern is official, registered, or has a particular status).
-
D.
isRegimentalTartanOf
Indicates that one tartan pattern is officially designated as the regimental tartan of a particular military regiment.
-
E.
principalTartanOf
Indicates that one entity is the officially recognized primary tartan associated with another entity, such as a clan, organization, or region.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:02 p.m.