Triple
T10337297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | الكتاب |
E243039
|
entity |
| Predicate | يُدرَّس في |
P48837
|
FINISHED |
| Object | أقسام اللغة العربية في الجامعات |
—
|
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: أقسام اللغة العربية في الجامعات | Statement: [الكتاب, يُدرَّس في, أقسام اللغة العربية في الجامعات]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: يُدرَّس في Context triple: [الكتاب, يُدرَّس في, أقسام اللغة العربية في الجامعات]
-
A.
hasTeaching
Indicates that one entity provides instruction or educational guidance to another entity.
-
B.
definedTeaching
Indicates that one entity has formally specified or established the teaching content, method, or curriculum for another entity.
-
C.
hasTeachingRole
Indicates that one entity holds a position or responsibility involving teaching or instruction in relation to another entity.
-
D.
hasTeachingContext
Indicates that an entity is associated with a specific educational or instructional setting in which teaching occurs.
-
E.
areTaughtIn
chosen
Indicates that certain subjects, courses, or topics are instructed or delivered within specific locations, classes, or educational settings.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:54 a.m.