Triple
T12017498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hosso sect |
E286062
|
entity |
| Predicate | scholarlyEmphasis |
P102810
|
FINISHED |
| Object | Scriptural exegesis |
—
|
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: Scriptural exegesis | Statement: [Hosso sect, scholarlyEmphasis, Scriptural exegesis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scholarlyEmphasis Context triple: [Hosso sect, scholarlyEmphasis, Scriptural exegesis]
-
A.
scholarlyView
Indicates that one entity holds an academic or research-based interpretation, opinion, or theoretical stance about another entity.
-
B.
scholarlyUse
Indicates that something is used for academic, educational, or research-related purposes.
-
C.
academicEmphasis
Indicates a focus or concentration of study or specialization within an academic program or curriculum.
-
D.
scholarlyWork
Indicates a relationship where an entity is a formal academic or research work produced, published, or recognized within a scholarly context.
-
E.
isScholarly
Indicates that an entity exhibits characteristics of academic rigor, research-based inquiry, and adherence to scholarly standards or conventions.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d91006e14081909838412df082f794 |
completed | April 10, 2026, 2:58 p.m. |
Created at: April 8, 2026, 9:47 p.m.