Triple
T11738349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shivneri Fort |
E279087
|
entity |
| Predicate | birthDateEvent |
P49450
|
FINISHED |
| Object | Shivaji Maharaj born here on 19 February 1630 (traditional date) |
—
|
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: Shivaji Maharaj born here on 19 February 1630 (traditional date) | Statement: [Shivneri Fort, birthDateEvent, Shivaji Maharaj born here on 19 February 1630 (traditional date)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthDateEvent Context triple: [Shivneri Fort, birthDateEvent, Shivaji Maharaj born here on 19 February 1630 (traditional date)]
-
A.
subjectBirthDate
Indicates the date on which the subject was born.
-
B.
dateOfBirth
Indicates the specific calendar date on which an individual or entity was born.
-
C.
birthEvent
chosen
Indicates an event in which an entity comes into existence by being born, typically linking the newborn to contextual details such as time, place, and participants.
-
D.
uncertainBirthDate
Indicates that the exact birth date of an entity is not known or is only approximately specified.
-
E.
hasBirthday
Indicates that an entity has a specific date on which its birth or founding is celebrated.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4ef1c4881909ad36dc27b1fe193 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.