Triple
T25156232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Iphigenia |
E626320
|
entity |
| Predicate | statusInHagiography |
P162568
|
FINISHED |
| Object | legendary figure |
—
|
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: legendary figure | Statement: [Saint Iphigenia, statusInHagiography, legendary figure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInHagiography Context triple: [Saint Iphigenia, statusInHagiography, legendary figure]
-
A.
inCanonizationStatus
Indicates that an entity has a specific status or stage within a formal canonization process.
-
B.
dateOfCanonizationStatus
Indicates the date on which an entity’s canonization status (such as being declared a saint or blessed) was formally conferred or recorded.
-
C.
martyrdomStatus
Indicates the state or condition of an entity with respect to being recognized or regarded as a martyr.
-
D.
hasSacredStatusSince
Indicates that an entity has held a recognized sacred or holy status starting from a specified point in time.
-
E.
canonizedIn
Indicates that an authority formally declared someone to be a saint or holy figure in a specified place or institution.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f627ad6d4c81909796d39d78e414f9 |
completed | May 2, 2026, 4:34 p.m. |
Created at: April 18, 2026, 6:30 a.m.