Triple
T29173510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Faustinus |
E739538
|
entity |
| Predicate | hasCompanionInMartyrdom |
P142509
|
FINISHED |
| Object | Saint Jovita |
—
|
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 Jovita | Statement: [Saint Faustinus, hasCompanionInMartyrdom, Saint Jovita]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompanionInMartyrdom Context triple: [Saint Faustinus, hasCompanionInMartyrdom, Saint Jovita]
-
A.
martyrAssociated
Indicates that there is a relationship of connection or involvement between an entity and a martyr, such as affiliation, support, or commemoration.
-
B.
martyrdomStatus
Indicates the state or condition of an entity with respect to being recognized or regarded as a martyr.
-
C.
martyrType
Indicates that one entity is classified as a specific type or category of martyr in relation to another entity.
-
D.
pairedMartyr
chosen
Indicates that two entities are linked through a shared or corresponding martyrdom, such that each is considered the martyr counterpart of the other.
-
E.
martyr
Indicates that an entity is killed or suffers greatly, typically for a belief, cause, or principle, often being regarded or treated as a martyr as a result.
- 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_69f07cb6394c8190ab7842c48e699e2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
Created at: April 28, 2026, 11:53 a.m.