Triple
T18964298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine Business and Consumer Court |
E463991
|
entity |
| Predicate | caseTypeIncludes |
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: [Maine Business and Consumer Court, caseTypeIncludes, contract disputes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseTypeIncludes Context triple: [Maine Business and Consumer Court, caseTypeIncludes, contract disputes]
-
A.
caseTypes
chosen
Indicates the types or categories of cases associated with or applicable to an entity or situation.
-
B.
hasTypeOfCase
Indicates that an entity is associated with or classified under a particular type or category of case.
-
C.
scienceCaseIncludes
Indicates that a science case encompasses, contains, or makes use of a particular element, component, or resource as part of its scope or definition.
-
D.
includesMatchType
Indicates that one entity’s set or collection contains an element with a specified type of match (e.g., exact, partial, or pattern-based) to another entity.
-
E.
hasCase
Indicates that one entity is involved in, associated with, or characterized by a particular case, instance, or occurrence represented by 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5d5365881909dcbb4988d273b24 |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon