Triple
T25226312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jinnah Mausoleum |
E632095
|
entity |
| Predicate | burialChamberContains |
P133253
|
FINISHED |
| Object | tomb of Liaquat Ali Khan |
—
|
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: tomb of Liaquat Ali Khan | Statement: [Jinnah Mausoleum, burialChamberContains, tomb of Liaquat Ali Khan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialChamberContains Context triple: [Jinnah Mausoleum, burialChamberContains, tomb of Liaquat Ali Khan]
-
A.
burialChamberStatus
Indicates the condition or state of a burial chamber, such as whether it is intact, disturbed, sealed, or otherwise altered.
-
B.
hasBurialChamberFor
chosen
Indicates that something (such as a structure or site) contains or is designated as a burial chamber intended for a particular individual or group.
-
C.
containsSarcophagusOf
Indicates that one entity physically houses or encloses the sarcophagus belonging to another entity.
-
D.
hasBurialChamberShape
Indicates that an entity’s burial chamber has a specific geometric or structural shape.
-
E.
foundInTomb
Indicates that an object or entity was discovered within a specific tomb or burial site.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 1:03 p.m.