Triple
T29249552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Anne’s Church in Warsaw |
E741523
|
entity |
| Predicate | consecratedTo |
P21434
|
FINISHED |
| Object | Saint Anne |
—
|
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 Anne | Statement: [St. Anne’s Church in Warsaw, consecratedTo, Saint Anne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consecratedTo Context triple: [St. Anne’s Church in Warsaw, consecratedTo, Saint Anne]
-
A.
consecratedBy
Indicates that one entity has been formally made sacred, dedicated, or set apart for religious use through a ritual or act performed by another entity.
-
B.
consecrated
chosen
Indicates that an entity has been formally dedicated or made sacred for a religious or holy purpose.
-
C.
coConsecratedWith
Indicates that two or more individuals were consecrated (e.g., as bishops) together in the same religious ceremony or event.
-
D.
consecratedInPresenceOf
Indicates that the act of consecration was performed while a specified person, group, or entity was present as a witness or participant.
-
E.
isDevotedTo
Indicates a strong, enduring commitment or dedication that one entity directs toward another.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 28, 2026, 12:33 p.m.