Triple
T26053380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kebalan |
E648047
|
entity |
| Predicate | hasTeachingInCommunityPrograms |
P167737
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kebalan, hasTeachingInCommunityPrograms, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTeachingInCommunityPrograms Context triple: [Kebalan, hasTeachingInCommunityPrograms, yes]
-
A.
hasTeachingActivities
Indicates that an entity engages in or is associated with teaching-related actions, roles, or responsibilities.
-
B.
hasTeachingActivity
Indicates that an entity engages in or is associated with a specific teaching-related activity or instructional role.
-
C.
hasTeaching
Indicates that one entity provides instruction or educational guidance to another entity.
-
D.
hasTeachingRole
Indicates that one entity holds a position or responsibility involving teaching or instruction in relation to another entity.
-
E.
hasTeachingMission
Indicates that an entity has a role, responsibility, or formal mandate to provide teaching or educational instruction to others.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 22, 2026, 9:11 a.m.