Triple
T27363942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | wildcat shoulder sleeve insignia |
E685903
|
entity |
| Predicate | wearerRequirement |
P137402
|
FINISHED |
| Object | assignment to 81st Infantry Division |
—
|
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: assignment to 81st Infantry Division | Statement: [wildcat shoulder sleeve insignia, wearerRequirement, assignment to 81st Infantry Division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wearerRequirement Context triple: [wildcat shoulder sleeve insignia, wearerRequirement, assignment to 81st Infantry Division]
-
A.
wearerMust
Indicates that a specified item or object is required to be worn by a particular entity under certain conditions or rules.
-
B.
wearerAssignmentRequirement
chosen
Indicates that a condition or rule specifies which wearer or type of wearer must be assigned to use or possess a particular item or resource.
-
C.
wearerType
Indicates the type or category of entity that is intended to wear or use the associated item.
-
D.
wearerStatus
Indicates the condition or role of an entity in its capacity as a wearer of something (e.g., clothing, equipment, or an accessory).
-
E.
wearerMayRetain
Indicates that the wearer is allowed to keep or continue possessing the item in question.
- 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.