Triple
T38499019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khalapur |
E919775
|
entity |
| Predicate | hasNearbyTourismType |
P120316
|
FINISHED |
| Object | hill stations |
—
|
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: hill stations | Statement: [Khalapur, hasNearbyTourismType, hill stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyTourismType Context triple: [Khalapur, hasNearbyTourismType, hill stations]
-
A.
hasAttractionNearby
Indicates that one entity is located close to another entity that serves as an attraction or point of interest.
-
B.
hasNearbySiteType
chosen
Indicates that one entity has another entity of a specified site type located in its close physical vicinity.
-
C.
hasNearbyHolidayPark
Indicates that one place or location is situated close to a holiday park.
-
D.
hasNearbyInfrastructureType
Indicates that an entity is located close to infrastructure of a specified type.
-
E.
nearbyTo
Indicates that one entity is located close in distance or position to 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00cbae75988190974f5b45a2e62326 |
completed | May 10, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_6a00cabe4c5881909cca5efbe494e0d1 |
completed | May 10, 2026, 6:13 p.m. |
Created at: May 3, 2026, 4:31 p.m.