Triple
T14693766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astute programme |
E345100
|
entity |
| Predicate | firstOfClassLaidDown |
P115381
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Astute programme, firstOfClassLaidDown, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOfClassLaidDown Context triple: [Astute programme, firstOfClassLaidDown, 1999]
-
A.
firstLaidDown
Indicates that one entity was the earliest to establish, formulate, or introduce another entity (such as a rule, idea, or structure).
-
B.
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.
-
C.
firstOccupied
Indicates that an entity was the initial or earliest occupant of a particular place, position, or resource.
-
D.
firstOrdinary
Indicates that the subject is the first entity to hold or occupy an ordinary (non-special, standard) position, role, or status in a given sequence or context.
-
E.
laidDownAs
Indicates that one entity has been formally established, stipulated, or prescribed as a rule, principle, or condition for another.
- 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_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. |
| PDg | Predicate description generation | batch_69de716d3aac8190aaa6dc1f099b86e8 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:28 a.m.