Triple
T26224001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bahuda Yatra |
E655839
|
entity |
| Predicate | takesPlaceInDistrict |
P128240
|
FINISHED |
| Object | Puri district |
—
|
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: Puri district | Statement: [Bahuda Yatra, takesPlaceInDistrict, Puri district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takesPlaceInDistrict Context triple: [Bahuda Yatra, takesPlaceInDistrict, Puri district]
-
A.
occursInDistrict
chosen
Indicates that an event or activity takes place within the boundaries of a specific district.
-
B.
takesPlaceInRegion
Indicates that an event or occurrence happens within the boundaries of a specified geographic or administrative region.
-
C.
basedInDistrict
Indicates that an entity is located or has its primary base of operations within a specific administrative district.
-
D.
tookPlaceInAdministrativeEntity
Indicates that an event or occurrence happened within the jurisdiction or boundaries of a specific administrative entity.
-
E.
appliedInDistrict
Indicates that an application or action was submitted or carried out within a specific administrative district.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d52254c8190baece694af79ff3a |
completed | May 2, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 8:57 p.m.