Triple
T14452873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principal Bench at Ahmedabad |
E358379
|
entity |
| Predicate | isPrimarySeatFor |
P63954
|
FINISHED |
| Object | filing of most cases before Gujarat High Court |
—
|
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: filing of most cases before Gujarat High Court | Statement: [Principal Bench at Ahmedabad, isPrimarySeatFor, filing of most cases before Gujarat High Court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimarySeatFor Context triple: [Principal Bench at Ahmedabad, isPrimarySeatFor, filing of most cases before Gujarat High Court]
-
A.
hasPrimarySeat
chosen
Indicates that one entity is designated as the main or principal seat, location, or position associated with another entity.
-
B.
hasSeatAt
Indicates that an entity occupies or holds a place, position, or membership within a specific group, body, or location.
-
C.
hasSeat
Indicates that one entity possesses, provides, or includes a seat for another entity.
-
D.
hasSecondSeat
Indicates that an entity possesses or includes a secondary seat in addition to a primary one.
-
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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de916244948190bb09d1bfc485ba50 |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.