Triple
T37167859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | supreme civil court |
E920835
|
entity |
| Predicate | handlesCasesSuchAs |
P81213
|
FINISHED |
| Object | contract disputes |
—
|
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: contract disputes | Statement: [supreme civil court, handlesCasesSuchAs, contract disputes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesCasesSuchAs Context triple: [supreme civil court, handlesCasesSuchAs, contract disputes]
-
A.
handlesCasesBefore
Indicates that one entity is responsible for dealing with or managing cases prior to another entity or before a specified point in a process.
-
B.
hasCase
Indicates that one entity is involved in, associated with, or characterized by a particular case, instance, or occurrence represented by another entity.
-
C.
hearsCasesAs
Indicates that one judicial body or judge reviews and adjudicates cases originating from another court or jurisdiction.
-
D.
treatsCaseAs
Indicates that one entity handles, regards, or processes another entity specifically as a case or instance within a particular context or framework.
-
E.
caseTypes
chosen
Indicates the types or categories of cases associated with or applicable to an entity or situation.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.