Triple
T18837344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoshang Shah |
E460697
|
entity |
| Predicate | tombArchitecturalStyle |
P607
|
FINISHED |
| Object | white marble Indo-Islamic mausoleum |
—
|
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: white marble Indo-Islamic mausoleum | Statement: [Hoshang Shah, tombArchitecturalStyle, white marble Indo-Islamic mausoleum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tombArchitecturalStyle Context triple: [Hoshang Shah, tombArchitecturalStyle, white marble Indo-Islamic mausoleum]
-
A.
associatedWithTombDecorationStyle
Indicates a relationship where something is linked to, characterized by, or connected with a particular style of tomb decoration.
-
B.
tombCategory
Indicates the classification or type of a tomb that an entity is associated with.
-
C.
tombDecoration
Indicates that something serves as an ornamental or symbolic adornment associated with a tomb.
-
D.
cemeteryStyle
Indicates the stylistic or design characteristics that define how a cemetery is arranged or presented.
-
E.
architecturalStyle
chosen
Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99e86388190957acaaab401b5cb |
completed | April 20, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.