Triple
T21208724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farncombe Church of England Infant School |
E522659
|
entity |
| Predicate | offersYearGroup |
P138206
|
FINISHED |
| Object | Year 1 |
—
|
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: Year 1 | Statement: [Farncombe Church of England Infant School, offersYearGroup, Year 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersYearGroup Context triple: [Farncombe Church of England Infant School, offersYearGroup, Year 1]
-
A.
offeredToYear
chosen
Indicates that something (such as a program, course, or opportunity) is made available or provided to entities associated with a specific year (e.g., academic year or calendar year).
-
B.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
C.
offersGradeRange
Indicates that an entity provides educational instruction or services spanning a specified range of grade levels.
-
D.
typicalEligibilityAge
Indicates the usual or standard age at which an entity qualifies for or becomes eligible for a particular status, benefit, or activity.
-
E.
ageGroupIndicated
Indicates that a specific age range or category is identified or assigned to an 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73436eb4c819082e05caf1ba52672 |
completed | April 21, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:25 p.m.