Triple
T34200099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Good Service Medal, Gold |
E877352
|
entity |
| Predicate | serviceRequirementQualifier |
P153173
|
FINISHED |
| Object | continuous 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: continuous service | Statement: [Good Service Medal, Gold, serviceRequirementQualifier, continuous service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceRequirementQualifier Context triple: [Good Service Medal, Gold, serviceRequirementQualifier, continuous service]
-
A.
serviceRequirementDetail
chosen
Indicates that a specific requirement or condition is associated with the provision or performance of a service.
-
B.
serviceUserRequirement
Indicates that a user has a specific requirement or need that a service is expected to fulfill.
-
C.
providedQualificationFor
Indicates that one entity supplied or granted a qualification, credential, or certification that another entity possesses or uses.
-
D.
evaluationRequirement
Indicates that one entity imposes or specifies conditions under which another entity must be assessed, tested, or evaluated.
-
E.
requiresAdditionalQualifier
Indicates that the relationship or statement is not sufficiently specific on its own and must be accompanied by an extra qualifying detail or condition to be properly interpreted.
- 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 1, 2026, 1:55 a.m.