Triple
T12266642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airman Battle Uniform |
E292362
|
entity |
| Predicate | patternInfluencedBy |
P44042
|
FINISHED |
| Object | tiger stripe camouflage |
—
|
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: tiger stripe camouflage | Statement: [Airman Battle Uniform, patternInfluencedBy, tiger stripe camouflage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patternInfluencedBy Context triple: [Airman Battle Uniform, patternInfluencedBy, tiger stripe camouflage]
-
A.
pattern
Indicates that one entity exhibits, follows, or is characterized by a particular recurring form, structure, or arrangement associated with another entity.
-
B.
patroonOf
Indicates a relationship in which one entity acts as a patron, sponsor, or protector providing support or resources to another entity.
-
C.
designInfluenceOn
chosen
Indicates that one design, designer, or design-related factor has an effect on shaping, guiding, or altering another design or design outcome.
-
D.
wereInfluencedBy
Indicates that one entity’s ideas, actions, or characteristics were shaped or affected by another entity.
-
E.
patternModifiedFor
Indicates that an existing pattern has been altered or adapted to create a new or updated version.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9380a5e78819086bd4dfe9a83d1f5 |
completed | April 10, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69d91c4a66cc819083ce6fcaf5042af6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.