Triple
T9324980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | juvenile courts |
E224363
|
entity |
| Predicate | primaryJurisdictionOver |
P808
|
FINISHED |
| Object | minors |
—
|
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: minors | Statement: [juvenile courts, primaryJurisdictionOver, minors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryJurisdictionOver Context triple: [juvenile courts, primaryJurisdictionOver, minors]
-
A.
claimsJurisdictionOver
Indicates that one authority or governing body asserts legal power or control over a particular area, matter, or entity.
-
B.
canonicalJurisdictionOf
Indicates that one entity holds official legal or ecclesiastical authority over another entity or domain as its recognized jurisdiction.
-
C.
definedJurisdictionOf
Indicates that one entity formally establishes or specifies the scope, boundaries, or authority of another entity’s jurisdiction.
-
D.
hasJurisdictionOver
chosen
Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
-
E.
affectedJurisdictionOver
Indicates that one entity’s authority, control, or legal power extends over and impacts the jurisdiction of 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_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. |
Created at: March 30, 2026, 7:38 p.m.