Triple
T4876134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defense Superior Service Medal |
E109207
|
entity |
| Predicate | serviceContext |
P25808
|
FINISHED |
| Object | joint service |
—
|
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: joint service | Statement: [Defense Superior Service Medal, serviceContext, joint service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceContext Context triple: [Defense Superior Service Medal, serviceContext, joint service]
-
A.
serviceEntryContext
Indicates the contextual circumstances or environment in which a particular service entry is created, recorded, or applied.
-
B.
serviceSystem
Indicates a relationship where one entity functions as a service system that provides, manages, or supports services for another entity.
-
C.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
-
D.
supplyContext
Indicates that one entity provides relevant background information or situational details that clarify or frame another entity, action, or statement.
-
E.
systemContext
chosen
Indicates the contextual conditions, settings, or environment within which a system operates or an interaction occurs.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c28e56081908ee411ac94c3769e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.