Triple
T2334215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryanston School |
E44272
|
entity |
| Predicate | emphasises |
P17414
|
FINISHED |
| Object | individual tutorial system |
—
|
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: individual tutorial system | Statement: [Bryanston School, emphasises, individual tutorial system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasises Context triple: [Bryanston School, emphasises, individual tutorial system]
-
A.
hasEmphasis
chosen
Indicates that one element is given special stress, importance, or prominence relative to others.
-
B.
expresses
Indicates that one entity conveys, communicates, or articulates a thought, feeling, or idea through another medium or form.
-
C.
imposes
Indicates that one entity enforces, applies, or places a rule, condition, burden, or obligation upon another entity.
-
D.
positionEmphasized
Indicates that a particular position, stance, or role is given special prominence or stress relative to others.
-
E.
closingEmphasis
Indicates that one entity concludes or reinforces another entity’s point, action, or message with particular stress or importance.
- 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_69a889132b488190bbb43ad4780ddd92 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abc6f75d888190a2e41edaa532e83f |
completed | March 7, 2026, 6:34 a.m. |
| PD | Predicate disambiguation | batch_69abc594087c819098100a10c5478a4b |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:51 p.m.