Triple
T16795136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disruptive Pattern Combat Uniform |
E408211
|
entity |
| Predicate | patternOptimizedFor |
P8034
|
FINISHED |
| Object | Australian bush |
—
|
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: Australian bush | Statement: [Disruptive Pattern Combat Uniform, patternOptimizedFor, Australian bush]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patternOptimizedFor Context triple: [Disruptive Pattern Combat Uniform, patternOptimizedFor, Australian bush]
-
A.
patternModifiedFor
Indicates that an existing pattern has been altered or adapted to create a new or updated version.
-
B.
pattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a particular recurring form, structure, or arrangement associated with another entity.
-
C.
patroonOf
Indicates a relationship in which one entity acts as a patron, sponsor, or protector providing support or resources to another entity.
-
D.
patternFamily
Indicates that one entity belongs to, or is categorized within, a family or group of related patterns defined by the other entity.
-
E.
kitPattern
Indicates the design or visual pattern featured on a team's kit or uniform.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2a96d888190a9876c3784bb7f95 |
completed | April 18, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.