Triple
T25987492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dispur |
E646240
|
entity |
| Predicate | hasJudicialBodyNearby |
P107940
|
FINISHED |
| Object | Gauhati High Court (located in Guwahati) |
—
|
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: Gauhati High Court (located in Guwahati) | Statement: [Dispur, hasJudicialBodyNearby, Gauhati High Court (located in Guwahati)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJudicialBodyNearby Context triple: [Dispur, hasJudicialBodyNearby, Gauhati High Court (located in Guwahati)]
-
A.
judicialProximity
chosen
Indicates a relationship where one entity is located near, adjacent to, or within a short distance of another in a judicial or court-related context.
-
B.
hasNearbyInnOfCourt
Indicates that one entity is located close to, or in the immediate vicinity of, an Inn of Court.
-
C.
courtBasedIn
Indicates that a particular court is located or headquartered in a specified place or jurisdiction.
-
D.
hasLawEnactedNearby
Indicates that a law has been officially enacted in a location that is geographically close to the referenced entity.
-
E.
hasCourts
Indicates that an entity possesses, contains, or is equipped with one or more courts (e.g., legal, sports, or judicial facilities).
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60545933081908d733c7bc49009f1 |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 8:55 a.m.