Triple
T4124963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 51st Battalion, Far North Queensland Regiment |
E92701
|
entity |
| Predicate | uniformColourPatch |
P54424
|
FINISHED |
| Object | black over light blue diamond |
—
|
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 over light blue diamond | Statement: [51st Battalion, Far North Queensland Regiment, uniformColourPatch, black over light blue diamond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uniformColourPatch Context triple: [51st Battalion, Far North Queensland Regiment, uniformColourPatch, black over light blue diamond]
-
A.
uniformFacingsColour
Indicates that the facings (such as cuffs, collars, or lapels) on a uniform share the same color.
-
B.
uniformBranchColor
Indicates that all branches of the referenced entity share the same color.
-
C.
usedUniformColor
Indicates that multiple entities share or employed the same uniform color in a given context.
-
D.
broadcastInColour
Indicates that a broadcast or transmission is presented in color rather than in black and white.
-
E.
colorDisplay
Indicates that one entity presents, shows, or renders the color associated with another entity.
- 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_69aed9685f70819086932777aec8d959 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af0245adbc81908b89a40850047975 |
completed | March 9, 2026, 5:24 p.m. |
Created at: March 9, 2026, 3:41 p.m.