Triple
T14762803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upton Court Grammar School |
E346911
|
entity |
| Predicate | isSelectiveOn |
P10787
|
FINISHED |
| Object | academic ability |
—
|
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: academic ability | Statement: [Upton Court Grammar School, isSelectiveOn, academic ability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSelectiveOn Context triple: [Upton Court Grammar School, isSelectiveOn, academic ability]
-
A.
isSelective
chosen
Indicates that the relationship or action involves choosing or affecting only certain specific entities or options while excluding others based on particular criteria.
-
B.
isSelectiveFire
Indicates that a firearm is capable of operating in multiple firing modes (such as semi-automatic and fully automatic) selectable by the user.
-
C.
hasSelectionFor
Indicates that one entity holds or specifies a chosen option, subset, or configuration on behalf of another entity.
-
D.
usedToSelect
Indicates that one entity serves as a criterion, tool, or basis for choosing or determining another entity.
-
E.
isPreferredWhen
Indicates that one option, condition, or entity is chosen or favored over others in a particular context or situation.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7f3a1608190b1b17624003a0c7f |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.