Triple
T3390118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Corps utility uniforms |
E71395
|
entity |
| Predicate | notAuthorizedFor |
P49355
|
FINISHED |
| Object | formal ceremonies |
—
|
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: formal ceremonies | Statement: [Marine Corps utility uniforms, notAuthorizedFor, formal ceremonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notAuthorizedFor Context triple: [Marine Corps utility uniforms, notAuthorizedFor, formal ceremonies]
-
A.
notAccessibleBy
Indicates that one entity cannot be reached, used, or obtained through another specified entity or means.
-
B.
canAuthorize
Indicates that one entity has the power or permission to grant approval or official permission for another entity to perform an action or access a resource.
-
C.
cannotGrant
Indicates that an entity lacks the authority, permission, or ability to confer a requested right, access, or resource to another entity.
-
D.
accessRestrictedTo
Indicates that access to a resource, location, or information is limited exclusively to a specified entity or group under defined conditions.
-
E.
cannotReview
Indicates that an entity is not permitted or able to perform a review of another entity or item.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb6682c708190b76a7a16cee7c5aa |
completed | March 8, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb2e426b88190b82d9830149b142e |
completed | March 8, 2026, 5:33 p.m. |
Created at: March 8, 2026, 3:14 p.m.