Triple
T9609951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Special Forces Group (Airborne) |
E232070
|
entity |
| Predicate | uniformDistinctiveItem |
P18730
|
FINISHED |
| Object | green beret |
—
|
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: green beret | Statement: [1st Special Forces Group (Airborne), uniformDistinctiveItem, green beret]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uniformDistinctiveItem Context triple: [1st Special Forces Group (Airborne), uniformDistinctiveItem, green beret]
-
A.
uniformDistinction
Indicates that a clear and consistent difference is maintained between two or more entities within a given context.
-
B.
uniformSpecialty
Indicates that multiple entities share the same specific specialty, expertise, or area of focus.
-
C.
wearsOnUniform
chosen
Indicates that an item is part of and is worn as a component of a uniform.
-
D.
hasInsigniaWornBy
Indicates that a particular insignia is worn by a specified entity (such as a person, group, or organization).
-
E.
combatDistinctionDevice
Indicates a special recognition or device awarded to denote distinguished performance or merit in combat-related actions or operations.
- 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_69ca8485a90c819094fe40b42fde9d70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a8469e081909c8fb7c84ffea2b3 |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.