Triple
T35550761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kothi Khas |
E1027352
|
entity |
| Predicate | locatedInFortCity |
P40
|
FINISHED |
| Object | Bharatpur Fort area |
—
|
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: Bharatpur Fort area | Statement: [Kothi Khas, locatedInFortCity, Bharatpur Fort area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInFortCity Context triple: [Kothi Khas, locatedInFortCity, Bharatpur Fort area]
-
A.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
isLocatedDowntown
Indicates that an entity is situated within the downtown area of a city or town.
-
C.
locatedInCityWithSignificance
Indicates that an entity is located in a city that holds particular importance or notable significance (e.g., historical, cultural, political, or economic).
-
D.
housedInCity
Indicates that one entity (such as a building, organization, or facility) is located within and contained by a particular city.
-
E.
locatedInCapital
Indicates that an entity is situated within the capital city of a specified region, country, or administrative area.
- 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_69f76e014fd481909e9f04ac603a2aa9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.