Triple
T26233184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parsi crematorium, Bombay |
E656093
|
entity |
| Predicate | burialOrCremationOf |
P25159
|
FINISHED |
| Object | Bhikaji Cama |
—
|
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: Bhikaji Cama | Statement: [Parsi crematorium, Bombay, burialOrCremationOf, Bhikaji Cama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialOrCremationOf Context triple: [Parsi crematorium, Bombay, burialOrCremationOf, Bhikaji Cama]
-
A.
cremation
Indicates that one entity performs or undergoes the process of reducing a dead body to ashes by burning.
-
B.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
C.
burialStatus
Indicates the state or condition of whether and how an entity has been buried.
-
D.
burialPolicy
Indicates the rules or arrangements governing how and under what conditions a person’s body is to be buried.
-
E.
usedForBurialOf
chosen
Indicates that something serves or is employed as a means, place, or object for burying a particular 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d88c7b0819096aa999f8f366dbd |
completed | May 2, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9 p.m.