Triple
T9325022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | juvenile courts |
E224363
|
entity |
| Predicate | proceduresVaryBy |
P87526
|
FINISHED |
| Object | jurisdiction |
—
|
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: jurisdiction | Statement: [juvenile courts, proceduresVaryBy, jurisdiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proceduresVaryBy Context triple: [juvenile courts, proceduresVaryBy, jurisdiction]
-
A.
usageVariesBy
Indicates that the way something is used differs depending on a specified factor, such as context, user, location, or conditions.
-
B.
typeOfProcedureHandled
Indicates the specific kind or category of procedure that an entity is responsible for managing or processing.
-
C.
termVariesBy
Indicates that the value or meaning of a term changes depending on a specified factor, such as context, dimension, or condition.
-
D.
hasSpecialProcedure
Indicates that a particular entity is associated with or governed by a designated special procedure or process.
-
E.
compositionVariesBy
Indicates that the composition of something differs depending on a specified factor, condition, or context.
- 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_69ca8426d48481909596360f7791c7dd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd36f77c808190aa5489c4305fd67d |
completed | April 1, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:38 p.m.