Triple
T26593633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English Bazar |
E667427
|
entity |
| Predicate | locatedNearHistoricCity |
P156483
|
FINISHED |
| Object | Gour |
—
|
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: Gour | Statement: [English Bazar, locatedNearHistoricCity, Gour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedNearHistoricCity Context triple: [English Bazar, locatedNearHistoricCity, Gour]
-
A.
historicallyLocatedNear
Indicates that, in a historical context, one entity was geographically situated close to another entity.
-
B.
hasHistoricCenterNearby
chosen
Indicates that one entity is located close to another entity that serves as a historic center or historically significant core area.
-
C.
passesHistoricCity
Indicates that a route, path, or entity travels through or goes by a city recognized for its historical significance.
-
D.
hasNearbyHistoricArea
Indicates that one entity is located close to another entity that is designated as a historic area.
-
E.
isFromCityWithHistoricArchitecture
Indicates that an entity originates from a city known for its historically significant or architecturally notable buildings and structures.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: April 27, 2026, 2:09 a.m.