Triple
T34294631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Good Service Medal, Bronze |
E879988
|
entity |
| Predicate | awardedForServiceLength |
P90636
|
FINISHED |
| Object | 10 years |
—
|
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: 10 years | Statement: [Good Service Medal, Bronze, awardedForServiceLength, 10 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardedForServiceLength Context triple: [Good Service Medal, Bronze, awardedForServiceLength, 10 years]
-
A.
typicalTimeInServiceToAttain
chosen
Indicates the usual duration of service required for an entity to reach or attain a specified status, level, or condition.
-
B.
maximumAgeAtAward
Indicates the highest age a recipient can be (or was) at the time an award is given.
-
C.
hasTimePeriodOfService
Indicates that an entity is associated with a specific span of time during which it provided service or was actively serving.
-
D.
typicalAwardDuration
Indicates the usual length of time for which an award is granted or remains valid.
-
E.
standardServiceAge
Indicates the typical or expected age at which a service is normally provided, used, or considered applicable.
- 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 1, 2026, 1:57 a.m.