Triple
T25340672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wallingford School |
E635400
|
entity |
| Predicate | hasEnrolmentType |
P26488
|
FINISHED |
| Object | non-selective |
—
|
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: non-selective | Statement: [Wallingford School, hasEnrolmentType, non-selective]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnrolmentType Context triple: [Wallingford School, hasEnrolmentType, non-selective]
-
A.
enrollmentType
chosen
Indicates the specific category or mode under which an entity is enrolled in a program, service, or system.
-
B.
hasGradeType
Indicates that an entity is associated with a particular category or type of grade (e.g., letter grade, pass/fail, percentage).
-
C.
hasEnrollmentPolicy
Indicates that there is a specific rule or set of rules governing who may enroll in, access, or participate in something and under what conditions.
-
D.
hasAttendanceType
Indicates the specific category or mode of attendance associated with an event or participant (e.g., in-person, virtual, hybrid).
-
E.
hasEnrollmentPattern
Indicates a relationship where an entity is associated with a specific pattern or structure governing how enrollments occur or are organized.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 1:32 p.m.