Triple
T9387478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polaris missile system |
E225939
|
entity |
| Predicate | UKRetirementDate |
P7188
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Polaris missile system, UKRetirementDate, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UKRetirementDate Context triple: [Polaris missile system, UKRetirementDate, 1990s]
-
A.
retirementDate
chosen
Indicates the date on which an entity stops its active role or service, typically marking the end of its professional or operational period.
-
B.
latestRetirementPensionStartAge
Indicates the most recent or maximum age at which an individual’s retirement pension payments are scheduled to begin.
-
C.
earliestRetirementPensionStartAge
Indicates the minimum age at which an individual is first allowed to begin receiving retirement pension benefits.
-
D.
retirementPensionNormalStartAge
Indicates the standard or default age at which an individual becomes eligible to begin receiving their retirement pension benefits.
-
E.
retirementYear
Indicates the specific year in which an entity retires or is officially considered retired.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50d562a48190875d9fe3aae25a2b |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:45 p.m.