Triple
T14385499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Marine Corps uniform system |
E356711
|
entity |
| Predicate | hasWearer |
P86572
|
FINISHED |
| Object | Marine Corps officer |
—
|
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: Marine Corps officer | Statement: [United States Marine Corps uniform system, hasWearer, Marine Corps officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWearer Context triple: [United States Marine Corps uniform system, hasWearer, Marine Corps officer]
-
A.
wearerStatus
Indicates the condition or role of an entity in its capacity as a wearer of something (e.g., clothing, equipment, or an accessory).
-
B.
wearerMust
Indicates that a specified item or object is required to be worn by a particular entity under certain conditions or rules.
-
C.
wearerType
Indicates the type or category of entity that is intended to wear or use the associated item.
-
D.
primaryWearer
chosen
Indicates that one entity is the main or principal user or wearer of another entity (such as an item or garment).
-
E.
wearerEntitlement
Indicates that an entity has the right or authorization to wear a particular item (such as clothing, equipment, or an accessory).
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9025cff881908c08224d90d9f750 |
completed | April 14, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.