Triple
T23117362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heanor Gate Spencer Academy |
E576793
|
entity |
| Predicate | servesMinimumAge |
P42793
|
FINISHED |
| Object | 11 |
—
|
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: 11 | Statement: [Heanor Gate Spencer Academy, servesMinimumAge, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesMinimumAge Context triple: [Heanor Gate Spencer Academy, servesMinimumAge, 11]
-
A.
setsMinimumAge
chosen
Indicates that an entity establishes the lowest permissible age required for participation, access, or eligibility in relation to another entity or activity.
-
B.
ageLimitAppliesAt
Indicates the specific age or point in time at which an age-related restriction or limit becomes effective for an entity.
-
C.
ageLimitYears
Indicates the maximum allowed age, expressed in years, for which something is valid, permitted, or applicable.
-
D.
maximumAgeRequirement
Indicates that there is an upper age limit that an entity must not exceed in order for a condition, participation, or eligibility to apply.
-
E.
legalAgeToPurchase
Indicates that an entity has reached the minimum legally permitted age to purchase a specified item or service.
- 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_69e245f6c2e881909a228fdcfeb7c7d3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e4d095081908bad99fab6eaadd0 |
completed | April 29, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:59 p.m.