Triple
T16961982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana small claims courts |
E411451
|
entity |
| Predicate | serviceOfProcess |
P125399
|
FINISHED |
| Object | required |
—
|
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: required | Statement: [Indiana small claims courts, serviceOfProcess, required]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceOfProcess Context triple: [Indiana small claims courts, serviceOfProcess, required]
-
A.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
-
B.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
-
C.
serviceIs
Indicates that one entity functions as a service of a specified type or category in relation to another entity.
-
D.
service
Indicates that one entity performs work, assistance, or functions to meet the needs or requests of another entity.
-
E.
serviceSystem
Indicates a relationship where one entity functions as a service system that provides, manages, or supports services for another entity.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d021c5508190b6e3106554c07a9c |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9cddf88190bc42709604047353 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:31 a.m.