Triple
T23364206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Capture Inquiry |
E593266
|
entity |
| Predicate | reportDeliveryDate |
P152434
|
FINISHED |
| Object | 2022-01-04 |
—
|
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: 2022-01-04 | Statement: [State Capture Inquiry, reportDeliveryDate, 2022-01-04]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportDeliveryDate Context triple: [State Capture Inquiry, reportDeliveryDate, 2022-01-04]
-
A.
deliveryDate
Indicates the specific date on which a product, service, or item is scheduled or expected to be delivered.
-
B.
finalDeliveryDate
Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
-
C.
deliveredAt
Indicates the specific time or location at which something (such as a message, product, or service) is delivered.
-
D.
deliveredDuring
Indicates that one entity was delivered within the time span defined by another entity or temporal interval.
-
E.
firstDeliveryDate
Indicates the date on which an item, service, or order is delivered for the first time.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0aac4248190a4663ed12aed6856 |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 5:31 p.m.