Triple
T14562143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jenne |
E341692
|
entity |
| Predicate | scholarlyActivity |
P114696
|
FINISHED |
| Object | Quranic education |
—
|
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: Quranic education | Statement: [Jenne, scholarlyActivity, Quranic education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scholarlyActivity Context triple: [Jenne, scholarlyActivity, Quranic education]
-
A.
scholarlyWork
Indicates a relationship where an entity is a formal academic or research work produced, published, or recognized within a scholarly context.
-
B.
publicationActivity
Indicates the act or process of producing and disseminating a work (such as a document, article, or media item) to an audience.
-
C.
scholarlyUse
Indicates that something is used for academic, educational, or research-related purposes.
-
D.
hasAcademicActivityType
Indicates that an academic activity is classified as belonging to a specific type or category of academic work.
-
E.
scholarlyView
Indicates that one entity holds an academic or research-based interpretation, opinion, or theoretical stance about another entity.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb38afa8881909c9151b7620949ae |
completed | April 14, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb5ac548190932f238e37271741 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:23 a.m.