Triple
T31507414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trident successor programme |
E803854
|
entity |
| Predicate | plannedEntryIntoService |
P26282
|
FINISHED |
| Object | early 2030s |
—
|
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: early 2030s | Statement: [Trident successor programme, plannedEntryIntoService, early 2030s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedEntryIntoService Context triple: [Trident successor programme, plannedEntryIntoService, early 2030s]
-
A.
plannedEntry
Indicates that an entity is scheduled or intended to enter another entity, context, or location at a planned future time.
-
B.
plannedService
Indicates that a service is scheduled or intended to be provided, but has not yet occurred.
-
C.
plannedAt
chosen
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
-
D.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
E.
serviceEntryDate
Indicates the date on which a service or duty officially began or was first entered into the record.
- 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_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 30, 2026, 9:48 p.m.