Triple
T3332837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fakenham Infant and Nursery School |
E70071
|
entity |
| Predicate | hasPupilCategory |
P29232
|
FINISHED |
| Object | co-educational |
—
|
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: co-educational | Statement: [Fakenham Infant and Nursery School, hasPupilCategory, co-educational]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPupilCategory Context triple: [Fakenham Infant and Nursery School, hasPupilCategory, co-educational]
-
A.
hasStudentCategory
chosen
Indicates that an entity is classified under a specific category or type of student.
-
B.
hasSchoolCategory
Indicates that an entity (such as a school or educational institution) is associated with a particular category or type of school.
-
C.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
D.
hasFormerPupilRole
Indicates that an entity previously held the role or position of a pupil or student in relation to another entity.
-
E.
hasProgramCategory
Indicates that a program is classified under a specific category or type of program.
- 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb194960081909333c855f06d8b03 |
completed | March 8, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69ada42c2ba8819091136805ce17b39d |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.