Triple
T29283397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brightwood College |
E742441
|
entity |
| Predicate | targetedStudents |
P11007
|
FINISHED |
| Object | career-focused students |
—
|
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: career-focused students | Statement: [Brightwood College, targetedStudents, career-focused students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetedStudents Context triple: [Brightwood College, targetedStudents, career-focused students]
-
A.
targetStudentsFrom
Indicates that an entity directs its efforts, services, or offerings specifically toward a defined group of students.
-
B.
targetStudentGroup
chosen
Indicates a relationship where something is directed, tailored, or intended specifically for a particular group of students.
-
C.
targetStudentService
Indicates a relationship where a particular student is the intended recipient or focus of a specific service or support action.
-
D.
targetsTeaching
Indicates that one entity is the intended focus or recipient of another entity’s teaching efforts or instructional activities.
-
E.
studentsAre
Indicates that certain entities hold the role or status of being students in relation to something or someone.
- 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_69f09121ed8c8190b4cb27be3619c262 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: April 28, 2026, 12:56 p.m.