Triple
T10821611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint George the Zograf |
E255382
|
entity |
| Predicate | traditionallyHonoredAs |
P74359
|
FINISHED |
| Object | martyr |
—
|
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: martyr | Statement: [Saint George the Zograf, traditionallyHonoredAs, martyr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyHonoredAs Context triple: [Saint George the Zograf, traditionallyHonoredAs, martyr]
-
A.
alsoHonoredAs
Indicates that an entity is additionally recognized or celebrated under another title, role, or form of honor beyond its primary designation.
-
B.
celebratedAs
chosen
Indicates that one entity is regarded, honored, or widely recognized as having a particular role, status, or distinction.
-
C.
feastDayHonors
Indicates that a particular feast day is dedicated to honoring or commemorating a specific person, group, or event.
-
D.
honoredOn
Indicates that an entity is formally recognized, celebrated, or commemorated on a specific date or occasion.
-
E.
honoredInDenomination
Indicates that an individual or entity is formally recognized, venerated, or given special honor within a particular religious denomination.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7344ae2688190bceabf41c79d298d |
completed | April 9, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:18 p.m.