Triple
T31507412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trident successor programme |
E803854
|
entity |
| Predicate | mainGateApproval |
P172259
|
FINISHED |
| Object | July 2016 |
—
|
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: July 2016 | Statement: [Trident successor programme, mainGateApproval, July 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainGateApproval Context triple: [Trident successor programme, mainGateApproval, July 2016]
-
A.
fundingMainGateApproval
Indicates that an entity has received primary authorization or approval to access or use a specific source of funding.
-
B.
hasGate
Indicates that one entity possesses, includes, or is equipped with a gate as part of its structure or configuration.
-
C.
hasGatekeeper
Indicates that one entity serves as a controlling or mediating gatekeeper for access to another entity.
-
D.
approvalProcessManagedBy
Indicates that the responsibility for overseeing and controlling the approval process is assigned to a specific managing entity.
-
E.
publicApproval
Indicates the degree to which the general public supports, agrees with, or has a favorable opinion of a person, action, policy, or entity.
- F. None of above. chosen
Provenance (4 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_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a915ead881909463ae46419c343e |
completed | May 3, 2026, 1:47 a.m. |
Created at: April 30, 2026, 9:48 p.m.