Triple
T31514743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stylianos |
E804035
|
entity |
| Predicate | orthodoxSaintConnection |
P43509
|
FINISHED |
| Object | Saint Stylianos of Paphlagonia |
—
|
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: Saint Stylianos of Paphlagonia | Statement: [Stylianos, orthodoxSaintConnection, Saint Stylianos of Paphlagonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orthodoxSaintConnection Context triple: [Stylianos, orthodoxSaintConnection, Saint Stylianos of Paphlagonia]
-
A.
linkedToSaint
chosen
Indicates that one entity has a direct association or connection with a saint.
-
B.
religiousFigure
Indicates that one entity is recognized or designated as a religious leader, authority, or sacred person in relation to another entity.
-
C.
saintName
Indicates that an entity has the specified name under which they are recognized or venerated as a saint.
-
D.
religiousFigureType
Indicates the specific role or category of a person recognized as a religious figure (e.g., priest, monk, prophet) within a religious context.
-
E.
associatedSaintOccupation
Indicates the occupation or role that is linked to or held by a particular saint.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a2578cb081908304c8d338fb5b81 |
completed | May 3, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:52 p.m.