Triple
T9334977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Martyrs |
E224620
|
entity |
| Predicate | commemoratedCollectivelyAs |
P58126
|
FINISHED |
| Object | all holy martyrs |
—
|
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: all holy martyrs | Statement: [the Martyrs, commemoratedCollectivelyAs, all holy martyrs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commemoratedCollectivelyAs Context triple: [the Martyrs, commemoratedCollectivelyAs, all holy martyrs]
-
A.
commemoratedBy
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
-
B.
commemoratedIn
Indicates that something is honored, remembered, or recognized within a particular work, event, place, or medium.
-
C.
commemoratedFor
Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
-
D.
commemoratesEventWith
Indicates that one entity serves as a memorial or tribute to a specific event, marking or honoring its occurrence.
-
E.
commemoratedGroup
chosen
Indicates that a group is honored, remembered, or recognized, typically through a memorial, event, or other commemorative act.
- 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_69ca84286fcc81909f6e7fd7a7e862a2 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd37ee53988190bcc76588edbc2858 |
completed | April 1, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69cc7a66aef08190b8d668cff5b04f5f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:39 p.m.