Triple
T27363944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | wildcat shoulder sleeve insignia |
E685903
|
entity |
| Predicate | insigniaClass |
P151455
|
FINISHED |
| Object | combat division patch |
—
|
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: combat division patch | Statement: [wildcat shoulder sleeve insignia, insigniaClass, combat division patch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: insigniaClass Context triple: [wildcat shoulder sleeve insignia, insigniaClass, combat division patch]
-
A.
insigniaName
Indicates the specific name or designation assigned to an insignia associated with an entity.
-
B.
insigniaCaption
Indicates the text that serves as a caption or explanatory label specifically for an insignia.
-
C.
insigniaUsedFor
Indicates that a particular insignia is employed or designated for a specific purpose, function, or use.
-
D.
insigniaCategory
chosen
Indicates the classification or type of an insignia within a defined system of insignia categories.
-
E.
insigniaContext
Indicates the contextual relationship in which an insignia is used, displayed, or holds meaning (such as organizational, temporal, or situational context).
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62c261bd0819096e201683858aa16 |
completed | May 2, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 11:55 a.m.