Triple
T14062976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anarkali Bazaar |
E338391
|
entity |
| Predicate | marketLayout |
P32581
|
FINISHED |
| Object | narrow lanes |
—
|
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: narrow lanes | Statement: [Anarkali Bazaar, marketLayout, narrow lanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketLayout Context triple: [Anarkali Bazaar, marketLayout, narrow lanes]
-
A.
stationLayout
Indicates the spatial arrangement and structural organization of elements within a station.
-
B.
layoutDetail
chosen
Indicates the specific arrangement or configuration details of how elements are laid out in relation to each other.
-
C.
urbanLayout
Indicates how the spatial arrangement, organization, and structure of buildings, streets, and public spaces relate to one another within an urban area.
-
D.
productLayout
Indicates how components or elements are spatially arranged and organized within a product or product-related space.
-
E.
marketContext
Indicates the broader economic, competitive, and situational conditions under which a product, service, or transaction is positioned or evaluated.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de568876308190840361dcaf10bd45 |
completed | April 14, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.