Triple
T22512979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pio da Pietrelcina |
E556566
|
entity |
| Predicate | stigmataReported |
P124516
|
FINISHED |
| Object | 1918-09-20 |
—
|
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: 1918-09-20 | Statement: [Pio da Pietrelcina, stigmataReported, 1918-09-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stigmataReported Context triple: [Pio da Pietrelcina, stigmataReported, 1918-09-20]
-
A.
madePublicConfessionAt
Indicates that an entity openly admitted or confessed something in a public setting at a specific time or place.
-
B.
containsConfession
Indicates that one entity includes or expresses an admission of guilt, wrongdoing, or previously concealed truth regarding another entity or situation.
-
C.
martyrdomStatus
Indicates the state or condition of an entity with respect to being recognized or regarded as a martyr.
-
D.
associatedConfession
Indicates a relationship where one entity is linked to a specific confession, admission, or statement acknowledging guilt or responsibility.
-
E.
evidenceOfDevotion
chosen
Indicates that one entity serves as proof or demonstration of another entity’s devotion or commitment.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d62bea48190aaf34aa93bb3f67b |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.