Triple
T34077696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Children’s Court of New South Wales |
E873951
|
entity |
| Predicate | ageJurisdictionUpperLimit |
P99503
|
FINISHED |
| Object | 18 years |
—
|
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: 18 years | Statement: [Children’s Court of New South Wales, ageJurisdictionUpperLimit, 18 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageJurisdictionUpperLimit Context triple: [Children’s Court of New South Wales, ageJurisdictionUpperLimit, 18 years]
-
A.
ageJurisdiction
Indicates that a specified legal or administrative authority has jurisdiction over matters related to a person's age.
-
B.
jurisdictionLimit
Indicates the maximum scope or boundary within which an authority, organization, or rule is legally empowered to operate or exercise control.
-
C.
ageLimitType
Indicates the type or category of age restriction that applies to an entity or activity.
-
D.
ageLimitYears
chosen
Indicates the maximum allowed age, expressed in years, for which something is valid, permitted, or applicable.
-
E.
minimumJurorAge
Indicates the minimum age requirement that an individual must meet to be eligible to serve as a juror.
- 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70bd3d9408190b405c4fa07634ae7 |
completed | May 3, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:52 a.m.