Triple
T38294868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Corps recruits |
E1022460
|
entity |
| Predicate | mustAdhereTo |
P190613
|
FINISHED |
| Object | Uniform Code of Military Justice |
—
|
NE NERFINISHED |
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: Uniform Code of Military Justice | Statement: [Marine Corps recruits, mustAdhereTo, Uniform Code of Military Justice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mustAdhereTo Context triple: [Marine Corps recruits, mustAdhereTo, Uniform Code of Military Justice]
-
A.
mustMeet
Indicates that one entity is required or obligated to have a meeting or encounter with another entity.
-
B.
mustRespect
Indicates that one entity is obligated to show respect or deference toward another entity.
-
C.
mustGrant
Indicates that one party is obligated to give or allow something (such as a right, permission, or resource) to another party.
-
D.
mustServe
Indicates that one entity is obligated or required to provide service or perform duties for another entity.
-
E.
mustBeUsed
Indicates that one entity is required or obligated to be utilized or applied in relation to another entity or context.
- 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fccbd6b7688190b746803cf78d5704 |
completed | May 7, 2026, 5:28 p.m. |
Created at: May 3, 2026, 4:30 p.m.