Triple
T1155889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Bench |
E23780
|
entity |
| Predicate | typeOfProceedings |
P25382
|
FINISHED |
| Object | collegial |
—
|
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: collegial | Statement: [Grand Bench, typeOfProceedings, collegial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfProceedings Context triple: [Grand Bench, typeOfProceedings, collegial]
-
A.
legalProcedureUsed
Indicates that a particular legal procedure or process is applied or employed in relation to a case, action, or legal matter.
-
B.
typeOfAppeals
Indicates the specific category or kind of appeals associated with or applied to a given case, decision, or legal action.
-
C.
hasTypeOfCourt
Indicates that an entity is associated with or classified by a specific type or category of court.
-
D.
typeOfLaw
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
-
E.
hasLegalProceeding
Indicates that there is a formal legal action, case, or proceeding involving the related entities.
- F. None of above. chosen
Provenance (4 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc912300819084c9c69783055a70 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb50d19c81908a98dbbb04a8906f |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bc47fce48190825d3a877251f789 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:44 p.m.