Triple
T1289296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Uhud |
E27507
|
entity |
| Predicate | lesson |
P28123
|
FINISHED |
| Object | importance of obeying the Prophet’s orders |
—
|
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: importance of obeying the Prophet’s orders | Statement: [Battle of Uhud, lesson, importance of obeying the Prophet’s orders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lesson Context triple: [Battle of Uhud, lesson, importance of obeying the Prophet’s orders]
-
A.
course
Indicates that an entity is an academic class or unit of instruction offered within an educational program.
-
B.
training
Indicates that one entity is teaching, coaching, or otherwise helping another entity acquire or improve a skill, behavior, or capability.
-
C.
section
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
D.
coreTeaching
Indicates that an entity serves as a primary or foundational teaching or instructional activity for another entity.
-
E.
courseShape
Indicates the geometric layout or configuration that defines the path or outline of a course.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0d4dfb081908c8825d6062b1d99 |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee41ca08190b0ad6f7ea40c0b62 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bfa205ec81909d8170b398345615 |
completed | March 1, 2026, 10:37 p.m. |
Created at: March 1, 2026, 7:51 p.m.