Triple
T34771015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qene school |
E1002360
|
entity |
| Predicate | hasTeacherRole |
P52943
|
FINISHED |
| Object | memhir (master) of Qene |
—
|
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: memhir (master) of Qene | Statement: [Qene school, hasTeacherRole, memhir (master) of Qene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTeacherRole Context triple: [Qene school, hasTeacherRole, memhir (master) of Qene]
-
A.
hasTeachingRole
Indicates that one entity holds a position or responsibility involving teaching or instruction in relation to another entity.
-
B.
roleWithTeacher
Indicates a relationship where one entity holds a specific role or position in relation to a teacher.
-
C.
hasTeacherType
Indicates that an entity is associated with a teacher characterized by a specific type or category (e.g., role, specialization, or employment status).
-
D.
hasTeacher
chosen
Indicates that one entity serves as an instructor or educator for another entity.
-
E.
hasTeachingAuthority
Indicates that one entity possesses the recognized power or right to teach, instruct, or provide formal education to another entity or within a specific context.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: May 3, 2026, 3:59 p.m.