Triple
T26647478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baba Shah Musafir |
E668956
|
entity |
| Predicate | hasTombAt |
P87990
|
FINISHED |
| Object | Panchakki complex, Aurangabad |
—
|
NE NERFINISHED |
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: Panchakki complex, Aurangabad | Statement: [Baba Shah Musafir, hasTombAt, Panchakki complex, Aurangabad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTombAt Context triple: [Baba Shah Musafir, hasTombAt, Panchakki complex, Aurangabad]
-
A.
hasTombs
chosen
Indicates that one entity possesses, contains, or is the location of one or more tombs associated with another entity.
-
B.
hasTombDesignation
Indicates that an entity has been assigned a specific formal designation or identifier for its tomb.
-
C.
tombLocatedIn
Indicates that a particular tomb is situated within or at a specified location or place.
-
D.
hasMausoleum
Indicates that one entity possesses, contains, or is associated with a mausoleum dedicated to another entity.
-
E.
hasGraveOccupant
Indicates that a grave is occupied by a specific person or entity.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 2:31 a.m.