Triple
T14959989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orissa High Court |
E373036
|
entity |
| Predicate | hasBenchStrengthType |
P23358
|
FINISHED |
| Object | Single judge benches |
—
|
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: Single judge benches | Statement: [Orissa High Court, hasBenchStrengthType, Single judge benches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBenchStrengthType Context triple: [Orissa High Court, hasBenchStrengthType, Single judge benches]
-
A.
hasBenchType
chosen
Indicates that an entity is associated with or characterized by a specific type or category of bench.
-
B.
hasBench
Indicates that one entity possesses, contains, or is equipped with a bench.
-
C.
hasAdditionalBenchesAt
Indicates that one location or facility includes extra benches situated at or associated with another specified place.
-
D.
hasStrengthDescriptor
Indicates that an entity is associated with a qualitative description of its strength or intensity.
-
E.
hasForceStrength
Indicates that one entity possesses a certain level or degree of physical or exerted force strength in relation to another entity or context.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6cd85bc81909040b7ff78f62554 |
completed | April 15, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:40 a.m.