Triple
T5074867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lal Bahadur Shastri |
E114368
|
entity |
| Predicate | TashkentDeclarationDate |
P2503
|
FINISHED |
| Object | 1966-01-10 |
—
|
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: 1966-01-10 | Statement: [Lal Bahadur Shastri, TashkentDeclarationDate, 1966-01-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TashkentDeclarationDate Context triple: [Lal Bahadur Shastri, TashkentDeclarationDate, 1966-01-10]
-
A.
treatyDate
chosen
Indicates the calendar date on which a treaty is formally agreed upon, signed, or comes into effect between parties.
-
B.
endDateAsPartOfTranscaucasianSFSR
Indicates the date on which something (such as a status, membership, or existence) ended while it was part of the Transcaucasian Soviet Federative Socialist Republic.
-
C.
treatySignedYear
Indicates the calendar year in which a specific treaty was formally signed.
-
D.
GenevaActSignedAt
Indicates that the signing of a Geneva Act took place at a specific location.
-
E.
annexationDate
Indicates the date on which one entity formally annexed or incorporated another entity into its territory or jurisdiction.
- 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_69bd443cf28c8190ad371d603563dbdd |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74d2243481908c1ae62f7123c4e9 |
completed | March 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.