Triple
T25963304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ekamra Kshetra |
E645598
|
entity |
| Predicate | influenceOnCityForm |
P128596
|
FINISHED |
| Object | temple-centered urban development of Bhubaneswar |
—
|
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: temple-centered urban development of Bhubaneswar | Statement: [Ekamra Kshetra, influenceOnCityForm, temple-centered urban development of Bhubaneswar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influenceOnCityForm Context triple: [Ekamra Kshetra, influenceOnCityForm, temple-centered urban development of Bhubaneswar]
-
A.
cityOfInfluence
Indicates the city that significantly shapes, impacts, or exerts influence over a given entity.
-
B.
urbanPlanningForm
Indicates the specific type or structure of urban planning approach applied to a place or development.
-
C.
inscriptionCity
Indicates the city where an inscription is or was made, located, or associated with.
-
D.
influencesSettlement
chosen
Indicates that one entity affects or shapes the establishment, development, or characteristics of a settlement.
-
E.
hasUrbanInfluence
Indicates that one entity exerts or reflects the characteristics, impact, or style of an urban area on another 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 22, 2026, 8:47 a.m.