Triple
T9763812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master Gunnery Sergeant |
E236732
|
entity |
| Predicate | insigniaUsage |
P14994
|
FINISHED |
| Object | worn on sleeves of Marine Corps uniforms |
—
|
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: worn on sleeves of Marine Corps uniforms | Statement: [Master Gunnery Sergeant, insigniaUsage, worn on sleeves of Marine Corps uniforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: insigniaUsage Context triple: [Master Gunnery Sergeant, insigniaUsage, worn on sleeves of Marine Corps uniforms]
-
A.
insigniaUsedFor
chosen
Indicates that a particular insignia is employed or designated for a specific purpose, function, or use.
-
B.
insigniaCaption
Indicates the text that serves as a caption or explanatory label specifically for an insignia.
-
C.
insigniaCenter
Indicates that one entity is positioned at or serves as the central element of another entity’s insignia or emblem.
-
D.
insigniaName
Indicates the specific name or designation assigned to an insignia associated with an entity.
-
E.
insigniaColorContext
Indicates the contextual circumstances or conditions under which a particular insignia color is used or holds its specific meaning.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda09ed54c8190a5879e14184cddf4 |
completed | April 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:25 p.m.