Triple
T21125936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star of the Sea Primary School |
E520556
|
entity |
| Predicate | hasPupilGrouping |
P90562
|
FINISHED |
| Object | co-educational (likely) |
—
|
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 (likely) | Statement: [Star of the Sea Primary School, hasPupilGrouping, co-educational (likely)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPupilGrouping Context triple: [Star of the Sea Primary School, hasPupilGrouping, co-educational (likely)]
-
A.
hasStudentCategory
Indicates that an entity is classified under a specific category or type of student.
-
B.
hasPupilsGender
chosen
Indicates that an entity has pupils whose gender is specified or characterized in some way.
-
C.
hasGradesOrClasses
Indicates that an entity is associated with academic evaluations or enrolled instructional sessions, such as grades received or classes taken.
-
D.
hasCentralGroup
Indicates that an entity possesses or is associated with a primary or central group within its structure or organization.
-
E.
hasPupilFutureRole
Indicates that a pupil is expected or designated to hold a specific role or position in the future.
- 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72238cf708190a4676c40deea2e46 |
completed | April 21, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.