Triple
T10466398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Will McKenzie |
E246806
|
entity |
| Predicate | academicPerformance |
P94190
|
FINISHED |
| Object | high-achieving |
—
|
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: high-achieving | Statement: [Will McKenzie, academicPerformance, high-achieving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: academicPerformance Context triple: [Will McKenzie, academicPerformance, high-achieving]
-
A.
studentsPerformAt
Indicates that students carry out or present a performance, activity, or task at a particular event, venue, or context.
-
B.
collegeAchievement
Indicates that an entity has attained a specific level of success, recognition, or accomplishment in a college or higher-education context.
-
C.
highSchoolAchievement
Indicates the level or nature of a person’s academic or related performance outcomes during their high school education.
-
D.
academicStatus
Indicates the educational or scholarly standing or level an entity holds within an academic context.
-
E.
schoolSubjectStrength
Indicates a relationship where an entity has a particular level of ability or proficiency in a specific school subject.
- F. None of above. chosen
Provenance (4 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5092d6d408190b6bda4d7ced4601e |
completed | April 7, 2026, 1:39 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:19 p.m.