Triple
T13146835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | probate division |
E312359
|
entity |
| Predicate | proceduresDefinedBy |
P108768
|
FINISHED |
| Object | statutes |
—
|
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: statutes | Statement: [probate division, proceduresDefinedBy, statutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proceduresDefinedBy Context triple: [probate division, proceduresDefinedBy, statutes]
-
A.
proceduresVaryBy
Indicates that the procedures or methods used differ depending on a specified factor, context, or category.
-
B.
typeOfProcedureHandled
Indicates the specific kind or category of procedure that an entity is responsible for managing or processing.
-
C.
endDefinedBy
Indicates that the termination or boundary of one entity is determined, specified, or constrained by another entity.
-
D.
procedureLanguage
Indicates the programming or formal language in which a given procedure, method, or algorithm is expressed or implemented.
-
E.
overseesProcedure
Indicates that one entity is responsible for supervising, managing, or directing the execution of a specific procedure performed by 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98ceeb22c8190a6be666031d9e5a4 |
completed | April 10, 2026, 11:51 p.m. |
Created at: April 9, 2026, 9:10 p.m.