Triple
T18457831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palam |
E450949
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Janakpuri |
—
|
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: Janakpuri | Statement: [Palam, locatedNear, Janakpuri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Janakpuri Context triple: [Palam, locatedNear, Janakpuri]
-
A.
Janakpuri
chosen
Janakpuri is a prominent residential and commercial neighborhood in West Delhi, India, known for its planned layout, markets, and metro connectivity.
-
B.
Baharampur
Baharampur is a major town and administrative center in the Murshidabad district of the Indian state of West Bengal, known for its historical significance and regional commerce.
-
C.
Ishwarpur
Ishwarpur is a municipality-level city located in Nepal’s Madhesh Province.
-
D.
Kakatpur
Kakatpur is a town in the Indian state of Odisha, known for the Maa Mangala Temple and its cultural and religious significance in the Puri region.
-
E.
Basantapur
Basantapur is a historic square in Kathmandu, Nepal, renowned for its old royal palace, traditional Newar architecture, and role as a central venue for major cultural festivals.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a7c18d88190ac17f58111722223 |
completed | April 19, 2026, 7:18 p.m. |
Created at: April 10, 2026, 11:31 a.m.