Triple
T13087007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eparchy of St. Mary, Queen of Peace of the USA and Canada |
E310361
|
entity |
| Predicate | hasMarianDedication |
P107974
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Eparchy of St. Mary, Queen of Peace of the USA and Canada, hasMarianDedication, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarianDedication Context triple: [Eparchy of St. Mary, Queen of Peace of the USA and Canada, hasMarianDedication, true]
-
A.
hasBasilicaDedication
Indicates that a basilica is formally dedicated to a particular figure, event, or concept.
-
B.
hasMonasteryDedicatedTo
Indicates that a place or institution possesses a monastery whose religious dedication is to a specific figure, deity, or sacred concept.
-
C.
hasPatronSaint
Indicates that one entity serves as the patron saint associated with, protecting, or representing another entity.
-
D.
isDevotedTo
Indicates a strong, enduring commitment or dedication that one entity directs toward another.
-
E.
hasAltarDedication
Indicates that an altar is dedicated to, in honor of, or in association with a particular entity or purpose.
- F. None of above. chosen
Provenance (4 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d981378dd08190b4f00e4e5df0e480 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98114a6508190b1e8e018bb5a068c |
completed | April 10, 2026, 11 p.m. |
Created at: April 9, 2026, 9:02 p.m.