Triple
T3036762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cracovia |
E83028
|
entity |
| Predicate | traditionalKitPattern |
P5928
|
FINISHED |
| Object | red 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: red and white vertical stripes | Statement: [Cracovia, traditionalKitPattern, red and white vertical stripes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalKitPattern Context triple: [Cracovia, traditionalKitPattern, red and white vertical stripes]
-
A.
kitPattern
chosen
Indicates the design or visual pattern featured on a team's kit or uniform.
-
B.
traditionalHomeKitPattern
Indicates that an entity follows a conventional or historically established pattern or style associated with traditional home kits or household arrangements.
-
C.
kitType
Indicates the specific category or configuration of a kit associated with an entity or activity.
-
D.
traditionalMaskType
Indicates the specific kind or category of traditional mask associated with an entity.
-
E.
traditionalCrossType
Indicates that one entity is related to another through a conventional or historically established type of cross or crossing relationship.
- 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_69ad8b2298908190a7cb4e9bdbf064d0 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b2cd4988190b52fe3616ecbe9ef |
completed | March 8, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69ad961e2a408190afb1759132701305 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.