Triple
T35296513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saidpur tehsil |
E1019383
|
entity |
| Predicate | hasRevenueCourt |
—
|
GENERATED |
| Object | tehsil-level revenue court |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevenueCourt Context triple: [Saidpur tehsil, hasRevenueCourt, tehsil-level revenue court]
-
A.
hasCourts
Indicates that an entity possesses, contains, or is equipped with one or more courts (e.g., legal, sports, or judicial facilities).
-
B.
hasCourtInEach
Indicates that an entity possesses or maintains a court in every member of a specified set of locations or jurisdictions.
-
C.
hasTribunal
Indicates that an entity is associated with or subject to a specific tribunal, such as a court or adjudicative body, that has authority over its cases or matters.
-
D.
hasStateCourt
Indicates that a given jurisdiction or region possesses an official court that operates at the state level.
-
E.
hasSeniorCourt
Indicates that one court is hierarchically subordinate to another court that serves as its senior or higher-level authority.
- F. None of above. chosen
Provenance (1 batch)
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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.