Triple
T9989375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allahabad Address |
E196846
|
entity |
| Predicate | deliveredOn |
P36795
|
FINISHED |
| Object | 1930 |
—
|
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: 1930 | Statement: [Allahabad Address, deliveredOn, 1930]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deliveredOn Context triple: [Allahabad Address, deliveredOn, 1930]
-
A.
deliveredAt
Indicates the specific time or location at which something (such as a message, product, or service) is delivered.
-
B.
deliveredDuring
Indicates that one entity was delivered within the time span defined by another entity or temporal interval.
-
C.
deliveryDate
chosen
Indicates the specific date on which a product, service, or item is scheduled or expected to be delivered.
-
D.
mustBeDeliveredBy
Indicates that one entity is required to be delivered or completed no later than a specified time, date, or deadline set by another entity.
-
E.
finalDeliveryDate
Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
- 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_69ca82f1678c819093d06320a05f16a4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdc79f3df08190ab3094ad1cd5490f |
completed | April 2, 2026, 1:34 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:50 p.m.