Triple
T269620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scorpion W2 |
E5601
|
entity |
| Predicate | camouflageType |
P1200
|
FINISHED |
| Object | multicam-style pattern |
—
|
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: multicam-style pattern | Statement: [Scorpion W2, camouflageType, multicam-style pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: camouflageType Context triple: [Scorpion W2, camouflageType, multicam-style pattern]
-
A.
camouflagePattern
chosen
Indicates that one entity has a surface or visual design intended to conceal it by blending with its surroundings or disrupting its outline.
-
B.
camouflageEffectiveness
Indicates how well one entity’s appearance or behavior conceals it from detection by another entity or sensing system.
-
C.
plumageFeature
Indicates a relationship where a specific characteristic or attribute is associated with an entity’s plumage (feathers).
-
D.
costumeType
Indicates the specific kind or category of costume associated with an entity.
-
E.
typeSpecies
Indicates that a species is the designated type species that defines and anchors the taxonomic concept of a higher-level group (such as a genus).
- 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_69a25853594c8190b05ec3a586ec88bf |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25db00ed48190be6f598807265356 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b70d99c819085d8381a313a2a34 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.