Triple
T34061999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomasina Coverly |
E873514
|
entity |
| Predicate | hasTeacherStudentRelationshipWith |
P137608
|
FINISHED |
| Object | Septimus Hodge |
—
|
NE NERFINISHED |
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: Septimus Hodge | Statement: [Thomasina Coverly, hasTeacherStudentRelationshipWith, Septimus Hodge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTeacherStudentRelationshipWith Context triple: [Thomasina Coverly, hasTeacherStudentRelationshipWith, Septimus Hodge]
-
A.
studentOrTeacherOf
chosen
Indicates that one entity is either a student of, or a teacher of, another entity within some educational or instructional context.
-
B.
hasStudents
Indicates that an entity (such as a class, school, or teacher) is associated with one or more students.
-
C.
hasTeacher
Indicates that one entity serves as an instructor or educator for another entity.
-
D.
hasTeacherType
Indicates that an entity is associated with a teacher characterized by a specific type or category (e.g., role, specialization, or employment status).
-
E.
relationshipToStudents
Indicates the type or nature of connection one entity has with students, such as role, affiliation, or responsibility toward them.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: May 1, 2026, 1:52 a.m.