Triple
T137711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunfermline Athletic F.C. |
E2783
|
entity |
| Predicate | kitPattern |
P5928
|
FINISHED |
| Object | black-and-white vertical stripes |
—
|
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: black-and-white vertical stripes | Statement: [Dunfermline Athletic F.C., kitPattern, black-and-white vertical stripes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kitPattern Context triple: [Dunfermline Athletic F.C., kitPattern, black-and-white vertical stripes]
-
A.
hatPattern
Indicates that one entity has a hat characterized by a specific pattern or design.
-
B.
camouflagePattern
Indicates that one entity has a surface or visual design intended to conceal it by blending with its surroundings or disrupting its outline.
-
C.
fieldPattern
Indicates a recurring or structured arrangement or configuration present within a field or area.
-
D.
typicalKey
Indicates that the referenced key is the standard or most commonly used key associated with an entity or context.
-
E.
drainagePattern
Indicates the characteristic spatial arrangement and connectivity of natural or artificial drainage features (such as streams, channels, or pipes) within an area.
- F. None of above. chosen
Provenance (4 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a6cab88190944c8f74d8d1605c |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a25652efdc8190b85b33735a9e6370 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2570f45bc81909ebba7ee5f602976 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.