Triple
T38129030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bijapur Sultanate |
E952164
|
entity |
| Predicate | architecturalMonument |
P193171
|
FINISHED |
| Object | Gol Gumbaz |
—
|
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: Gol Gumbaz | Statement: [Bijapur Sultanate, architecturalMonument, Gol Gumbaz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architecturalMonument Context triple: [Bijapur Sultanate, architecturalMonument, Gol Gumbaz]
-
A.
builtMonument
Indicates that one entity constructed or created a monument in honor of, or related to, another entity.
-
B.
architecturalComplex
Indicates a relationship where multiple architectural structures or elements are grouped and function together as a single, integrated complex.
-
C.
monumentType
Indicates the specific kind or category of monument that an entity is classified as.
-
D.
placeOfMonument
Indicates the location where a monument is situated or established.
-
E.
knownMonuments
Indicates that an entity is recognized or identified as a monument by another entity or within a given context.
- F. None of above. chosen
Provenance (4 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: May 3, 2026, 4:21 p.m.