Triple
T26990520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Navy uniforms |
E679849
|
entity |
| Predicate | hasWearerGroup |
P162498
|
FINISHED |
| Object | 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: officer | Statement: [U.S. Navy uniforms, hasWearerGroup, officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWearerGroup Context triple: [U.S. Navy uniforms, hasWearerGroup, officer]
-
A.
hasIntendedWearer
Indicates that an item is associated with the person or entity it is meant or designed to be worn by.
-
B.
wearerEntitlement
Indicates that an entity has the right or authorization to wear a particular item (such as clothing, equipment, or an accessory).
-
C.
wearerMust
Indicates that a specified item or object is required to be worn by a particular entity under certain conditions or rules.
-
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.
wearerAssignmentRequirement
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.
- F. None of above. chosen
Provenance (4 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f625402d808190be8279d895d2b27f |
completed | May 2, 2026, 4:24 p.m. |
Created at: April 27, 2026, 6:51 a.m.