Triple
T29926687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Philip |
E760098
|
entity |
| Predicate | traditionallyMartyredInRegion |
P67818
|
FINISHED |
| Object | Phrygia |
—
|
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: Phrygia | Statement: [Saint Philip, traditionallyMartyredInRegion, Phrygia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyMartyredInRegion Context triple: [Saint Philip, traditionallyMartyredInRegion, Phrygia]
-
A.
traditionallyMartyredWith
Indicates that an entity is customarily believed or depicted to have been martyred using a particular method, instrument, or circumstance.
-
B.
martyrdomDateTradition
Indicates the date of a person's martyrdom as preserved or assigned in a particular religious or historical tradition.
-
C.
martyredUnder
Indicates that an entity was killed or executed as a martyr during the rule, authority, or actions of another entity.
-
D.
traditionalMartyrdomSiteOf
chosen
Indicates that a place is traditionally regarded as the location where a particular individual was martyred.
-
E.
martyrAssociated
Indicates that there is a relationship of connection or involvement between an entity and a martyr, such as affiliation, support, or commemoration.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: April 29, 2026, 6:16 p.m.