Triple
T1371034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collingwood Football Club |
E30112
|
entity |
| Predicate | guernseyPattern |
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: [Collingwood Football Club, guernseyPattern, black and white vertical stripes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guernseyPattern Context triple: [Collingwood Football Club, guernseyPattern, black and white vertical stripes]
-
A.
kitPattern
chosen
Indicates the design or visual pattern featured on a team's kit or uniform.
-
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.
featuredUnionJackVariant
Indicates that an entity prominently displays or uses a specific variant of the Union Jack as a key identifying or decorative feature.
-
D.
jersey
Indicates that one entity is the jersey (sports uniform top) associated with, worn by, or representing another entity.
-
E.
tartan
Indicates that something has a tartan pattern or is characterized by a tartan design.
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2d7b6008190bc0303b56959ba56 |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befb08b88190be966fa1aadd4bcd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.