Triple
T33322595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nant Peris |
E853177
|
entity |
| Predicate | dedicatedToSaint |
P54136
|
FINISHED |
| Object | Saint Peris |
—
|
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 Peris | Statement: [Nant Peris, dedicatedToSaint, Saint Peris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dedicatedToSaint Context triple: [Nant Peris, dedicatedToSaint, Saint Peris]
-
A.
isDevotedTo
Indicates a strong, enduring commitment or dedication that one entity directs toward another.
-
B.
dedicatesLifeTo
Indicates devoting one’s time, effort, and primary purpose over an extended period to a particular person, cause, goal, or activity.
-
C.
liturgicalDedication
chosen
Indicates that something (typically a religious building, object, or time) is formally dedicated or consecrated for use in a specific liturgical or worship context.
-
D.
dedicatedToCharacter
Indicates that something (such as a work, item, or effort) is formally devoted or addressed in honor of a specific character.
-
E.
dedicatedOnOccasionOf
Indicates that something (typically a work, object, or event) is formally dedicated in connection with or to commemorate a particular occasion.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:33 a.m.