Triple
T26887832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manoppello |
E677090
|
entity |
| Predicate | hasReligiousRelic |
P128939
|
FINISHED |
| Object | Veil of Manoppello |
—
|
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: Veil of Manoppello | Statement: [Manoppello, hasReligiousRelic, Veil of Manoppello]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousRelic Context triple: [Manoppello, hasReligiousRelic, Veil of Manoppello]
-
A.
hasReligiousObject
chosen
Indicates that an entity possesses, is associated with, or contains a religious object (such as an artifact, symbol, or item used in religious practice).
-
B.
relicsAssociatedWith
Indicates a relationship where certain relics are connected or linked to a particular entity, context, or subject (such as a person, place, event, or tradition).
-
C.
associatedReligionForRelic
Indicates the religion with which a particular relic is associated.
-
D.
containsRelic
Indicates that one entity holds, includes, or has within it a relic.
-
E.
hasReligiousSite
Indicates that a location or entity possesses, contains, or is associated with a religious site such as a temple, church, mosque, shrine, or similar place of worship.
- 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: April 27, 2026, 5:43 a.m.