Triple
T31116465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cholistan Desert Jeep Rally |
E793100
|
entity |
| Predicate | notableCityAccess |
P207357
|
FINISHED |
| Object | Bahawalpur |
E224999
|
NE 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: Bahawalpur | Statement: [Cholistan Desert Jeep Rally, notableCityAccess, Bahawalpur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCityAccess Context triple: [Cholistan Desert Jeep Rally, notableCityAccess, Bahawalpur]
-
A.
notableCityIncluded
Indicates that a notable or significant city is contained within, or is part of, a larger geographic or administrative entity.
-
B.
notableInCity
Indicates that an entity is particularly prominent, recognized, or significant within a specific city.
-
C.
notableTerminusCity
Indicates that a city is notably recognized as a terminus (endpoint) of a route, line, or network.
-
D.
notableCityCommunity
Indicates a relationship where a city is notably associated with, recognized by, or significantly connected to a particular community.
-
E.
notableCityCenter
Indicates that a location serves as a prominent or significant central area within a city.
- F. None of above. chosen
Provenance (5 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f3b613034819097cc2227c6a24cc4 |
completed | June 14, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:04 p.m.