Triple
T5943053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Padre Pio |
E132212
|
entity |
| Predicate | allegedCharism |
P49815
|
FINISHED |
| Object | bilocation |
—
|
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: bilocation | Statement: [Padre Pio, allegedCharism, bilocation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedCharism Context triple: [Padre Pio, allegedCharism, bilocation]
-
A.
soteriologicalClaim
Indicates a relationship where an entity asserts or expresses a claim about salvation, redemption, or the means by which such spiritual deliverance is achieved.
-
B.
allegedUse
chosen
Indicates that something is claimed or suspected to have been used, without confirming that the use actually occurred.
-
C.
allegedImpostor
Indicates that one entity is claimed or suspected to be fraudulently posing as another entity.
-
D.
orderCharism
Indicates that one entity assigns or recognizes a specific charism, spiritual gift, or distinctive grace associated with a religious order in relation to another entity.
-
E.
foundingCharism
Indicates the distinctive spiritual focus, mission, or guiding gift that characterizes the founding identity of a religious community or organization.
- 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_69c00869d3308190af89b2453e0f7546 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0335806788190b6488ca8b73f7a63 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:01 p.m.