Triple
T31507415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trident successor programme |
E803854
|
entity |
| Predicate | plannedServiceLife |
P75499
|
FINISHED |
| Object | into the 2060s |
—
|
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: into the 2060s | Statement: [Trident successor programme, plannedServiceLife, into the 2060s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedServiceLife Context triple: [Trident successor programme, plannedServiceLife, into the 2060s]
-
A.
serviceLifeTarget
chosen
Indicates the intended or planned duration of time that a service, asset, or component is expected to remain in use or perform its function.
-
B.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
-
C.
durationOfUse
Indicates the length of time for which something is used or remains in use.
-
D.
durationInYears
Indicates the length of time associated with something, measured in whole or fractional years.
-
E.
plannedService
Indicates that a service is scheduled or intended to be provided, but has not yet occurred.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 30, 2026, 9:48 p.m.