Triple
T14693767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astute programme |
E345100
|
entity |
| Predicate | firstOfClassLaunched |
P69473
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Astute programme, firstOfClassLaunched, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOfClassLaunched Context triple: [Astute programme, firstOfClassLaunched, 2007]
-
A.
firstClassRuns
Indicates that the subject has participated in official first-class cricket matches, with the object specifying the number or record of such runs scored.
-
B.
firstModuleLaunch
Indicates the event or relationship where the initial module of a system, project, or mission is launched or activated for the first time.
-
C.
firstTestLaunch
chosen
Indicates that an entity’s initial test launch event occurs, marking the first time it is experimentally deployed or sent into operation.
-
D.
launchedFirstUnit
Indicates that one entity initiated and deployed the first unit of something (e.g., product, system, or mission) before any others.
-
E.
launchedWith
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb586e7108190be644db9cf9a4d99 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.