Triple
T34200091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Good Service Medal, Gold |
E877352
|
entity |
| Predicate | serviceTypeRecognised |
P53961
|
FINISHED |
| Object | permanent force 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: permanent force service | Statement: [Good Service Medal, Gold, serviceTypeRecognised, permanent force service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceTypeRecognised Context triple: [Good Service Medal, Gold, serviceTypeRecognised, permanent force service]
-
A.
serviceIs
Indicates that one entity functions as a service of a specified type or category in relation to another entity.
-
B.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
C.
serviceProviderType
Indicates the category or kind of service provider associated with an entity or transaction.
-
D.
serviceModuleType
Indicates the type or category of a service module associated with an entity or system.
-
E.
appliesToServiceType
chosen
Indicates that something is relevant or applicable specifically to a particular type or category of service.
- 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_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 1, 2026, 1:55 a.m.