Triple
T27029543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hwaeom |
E680880
|
entity |
| Predicate | prominentExegete |
P23020
|
FINISHED |
| Object | Wonhyo |
—
|
NE NERFINISHED |
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: Wonhyo | Statement: [Hwaeom, prominentExegete, Wonhyo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prominentExegete Context triple: [Hwaeom, prominentExegete, Wonhyo]
-
A.
notableTheologianTradition
Indicates that a theologian is notably associated with, or recognized as a significant figure within, a particular religious or theological tradition.
-
B.
scripturalExpertise
Indicates a relationship where one entity possesses specialized knowledge or authoritative understanding of religious scriptures in relation to another entity or context.
-
C.
associatedTheologian
chosen
Indicates a relationship where a theologian is connected or linked to a particular subject, work, institution, or context.
-
D.
notableHebrewTranslator
Indicates that one entity is recognized for having translated works into Hebrew or from Hebrew in a particularly significant or distinguished way.
-
E.
hasExegesisBy
Indicates that an entity (such as a text or passage) is the subject of an exegesis authored or provided by another entity.
- 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 7:13 a.m.