Triple
T942485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chamber of Summary Procedure of the International Court of Justice |
E20336
|
entity |
| Predicate | typeOfProcedure |
P7077
|
FINISHED |
| Object | summary procedure |
—
|
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: summary procedure | Statement: [Chamber of Summary Procedure of the International Court of Justice, typeOfProcedure, summary procedure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfProcedure Context triple: [Chamber of Summary Procedure of the International Court of Justice, typeOfProcedure, summary procedure]
-
A.
typeOfOperation
Indicates the specific kind or category of operation being performed or referenced in a given context.
-
B.
processType
Indicates the specific kind or category of process that an entity or activity belongs to.
-
C.
legalProcedureUsed
chosen
Indicates that a particular legal procedure or process is applied or employed in relation to a case, action, or legal matter.
-
D.
operationType
Indicates the specific kind of operation or action being performed or recorded in the relationship between entities.
-
E.
practiceType
Indicates the specific kind or category of practice associated with an entity or activity.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3a1a4888190997adf56eb761431 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b29dc8dc8190b9d33f70f8563d61 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.