Triple
T38018821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherghati |
E948565
|
entity |
| Predicate | hasNearbyTouristPlace |
P61270
|
FINISHED |
| Object | Bodh Gaya |
—
|
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: Bodh Gaya | Statement: [Sherghati, hasNearbyTouristPlace, Bodh Gaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyTouristPlace Context triple: [Sherghati, hasNearbyTouristPlace, Bodh Gaya]
-
A.
hasAttractionNearby
Indicates that one entity is located close to another entity that serves as an attraction or point of interest.
-
B.
nearbyLocation
chosen
Indicates that one location is situated close to another location in physical space.
-
C.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
D.
nearestTouristDestination
Indicates that one location is the closest tourist destination to another specified location.
-
E.
nearbyCurrent
Indicates that one entity is located close to another entity at the present moment or in the current context.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00b6199c348190b1e90375f737d026 |
completed | May 10, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_6a00b5169a7881909a07167c4188731f |
completed | May 10, 2026, 4:40 p.m. |
Created at: May 3, 2026, 4:20 p.m.