Triple
T25888455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Stewart tartan |
E652258
|
entity |
| Predicate | belongsToTartanFamily |
P4276
|
FINISHED |
| Object | Stewart tartans |
—
|
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: Stewart tartans | Statement: [Black Stewart tartan, belongsToTartanFamily, Stewart tartans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToTartanFamily Context triple: [Black Stewart tartan, belongsToTartanFamily, Stewart tartans]
-
A.
sharesClanTartanWith
Indicates that two entities belong to clans that use the same tartan pattern.
-
B.
isRegimentalTartanOf
Indicates that one tartan pattern is officially designated as the regimental tartan of a particular military regiment.
-
C.
hasHeraldicFamily
Indicates that an entity is associated with a particular heraldic family or lineage, typically sharing the same coat of arms or heraldic identity.
-
D.
principalTartanOf
Indicates that one entity is the officially recognized primary tartan associated with another entity, such as a clan, organization, or region.
-
E.
belongsToFamily
chosen
Indicates that an entity is a member of, or is associated as part of, a specific family group.
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 22, 2026, 8:18 a.m.