Triple
T19782980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Meritorious Unit Award |
E475183
|
entity |
| Predicate | isJointServiceDecoration |
P137311
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Joint Meritorious Unit Award, isJointServiceDecoration, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isJointServiceDecoration Context triple: [Joint Meritorious Unit Award, isJointServiceDecoration, true]
-
A.
isStateDecoration
Indicates that an item is an official decoration or honor conferred by a state or government authority.
-
B.
isJointBase
Indicates that two or more components share a common base or foundation point.
-
C.
containsDecorationFrom
Indicates that one entity includes or incorporates a decorative element that originates from another entity.
-
D.
isJointBaseUnder
Indicates that one base or installation operates under the shared authority or administration of multiple organizations or services.
-
E.
isJointPosition
Indicates that an entity occupies or specifies a particular position or configuration within a joint (e.g., in a mechanical, robotic, or anatomical system).
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653852e848190b8971981a164e8f9 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bcf41c8190b685b5adf46a60fc |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:49 p.m.