Triple
T37087770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jodhpur bench of the Rajasthan High Court |
E918335
|
entity |
| Predicate | isPrincipalSeat |
P63954
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
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: true | Statement: [Jodhpur bench of the Rajasthan High Court, isPrincipalSeat, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrincipalSeat Context triple: [Jodhpur bench of the Rajasthan High Court, isPrincipalSeat, true]
-
A.
hasPrimarySeat
chosen
Indicates that one entity is designated as the main or principal seat, location, or position associated with another entity.
-
B.
isSeatWithin
Indicates that one seat is located inside the spatial bounds or interior area defined by another object or region.
-
C.
isSafeSeatFor
Indicates that one entity is a suitable and secure seating option for another entity, posing no unacceptable risk or harm.
-
D.
isAtLargeSeat
Indicates that an individual holds or occupies an at-large seat, representing a broad constituency rather than a specific district or sub-area.
-
E.
seatIs
Indicates that one entity functions as the seat or seating position of another entity.
- 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: May 3, 2026, 4:14 p.m.