Triple
T9325023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | juvenile courts |
E224363
|
entity |
| Predicate | ageLimitVariesBy |
P65562
|
FINISHED |
| Object | country |
—
|
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: country | Statement: [juvenile courts, ageLimitVariesBy, country]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageLimitVariesBy Context triple: [juvenile courts, ageLimitVariesBy, country]
-
A.
ageLimitVariesFor
chosen
Indicates that the applicable age limit differs depending on the specific context, condition, or entity involved.
-
B.
ageLimitAppliesAt
Indicates the specific age or point in time at which an age-related restriction or limit becomes effective for an entity.
-
C.
ageLimitType
Indicates the type or category of age restriction that applies to an entity or activity.
-
D.
ageLimitIntroduced
Indicates that a specific age restriction or minimum/maximum age requirement has been formally established or put into effect for something.
-
E.
hasAgeGuidelines
Indicates that there are specified age-related rules or recommendations governing how something should be accessed, used, or engaged with.
- 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.