Triple
T3698465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travancore |
E78513
|
entity |
| Predicate | accessionDate |
P49458
|
FINISHED |
| Object | 1949-07-01 |
—
|
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: 1949-07-01 | Statement: [Travancore, accessionDate, 1949-07-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessionDate Context triple: [Travancore, accessionDate, 1949-07-01]
-
A.
acquisitionDate
Indicates the date on which one entity formally acquires or takes ownership of another entity.
-
B.
accessionAnniversaryOf
Indicates the date or event marking the anniversary of when an entity formally assumed a position, title, or membership.
-
C.
acknowledgmentDate
Indicates the date on which an acknowledgment of something (such as receipt, notice, or information) is formally recorded or recognized.
-
D.
admissionDate
Indicates the date on which an entity (such as a person, application, or item) is formally admitted, accepted, or entered into a system or institution.
-
E.
accessionYear
Indicates the calendar year in which an item, record, or entity was formally added to or registered within a collection, system, or institution.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc512ba188190a15bcacafac3f476 |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb903be308190a8f1925f99e67c68 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:26 p.m.