Triple
T29555946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bilaspur division (Chhattisgarh) |
E749905
|
entity |
| Predicate | hasHighCourtSeatNearby |
P193836
|
FINISHED |
| Object | Bilaspur |
—
|
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: Bilaspur | Statement: [Bilaspur division (Chhattisgarh), hasHighCourtSeatNearby, Bilaspur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighCourtSeatNearby Context triple: [Bilaspur division (Chhattisgarh), hasHighCourtSeatNearby, Bilaspur]
-
A.
highCourtSeat
Indicates that a location serves as the official seat or headquarters of a high court.
-
B.
hasCourthouse
Indicates that a location or jurisdiction possesses or contains a courthouse.
-
C.
hasNearbyInnOfCourt
Indicates that one entity is located close to, or in the immediate vicinity of, an Inn of Court.
-
D.
hasCourts
Indicates that an entity possesses, contains, or is equipped with one or more courts (e.g., legal, sports, or judicial facilities).
-
E.
courtBasedIn
Indicates that a particular court is located or headquartered in a specified place or jurisdiction.
- F. None of above. chosen
Provenance (4 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fd57b9cdec81908536c4159e375931 |
completed | May 8, 2026, 3:25 a.m. |
Created at: April 28, 2026, 5:16 p.m.