Triple
T26884736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grey Court School |
E677009
|
entity |
| Predicate | isMixedAbility |
P141983
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Grey Court School, isMixedAbility, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMixedAbility Context triple: [Grey Court School, isMixedAbility, yes]
-
A.
hasMixedAbilityIntake
chosen
Indicates that a group or program includes participants with a range of ability levels rather than a single, uniform level.
-
B.
hasIceOrMixedGrade
Indicates that a road segment or surface currently has icy conditions or a mixture of ice and other surface states (e.g., wet, slushy, or bare).
-
C.
includesMixedSexRace
Indicates that the group or context involves individuals of more than one sex and more than one race.
-
D.
mixedDiscipline
Indicates that an entity involves or combines multiple distinct disciplines, fields, or areas of expertise within a single context or activity.
-
E.
mixedAt
Indicates that one entity has been combined or blended together with another entity (or entities), typically to form a mixture at a specific time or place.
- 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61f61ee6c81908213e768ab561331 |
completed | May 2, 2026, 3:59 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:41 a.m.