Triple
T29200188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Juan |
E740245
|
entity |
| Predicate | usedInChurchDedications |
P38130
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [San Juan, usedInChurchDedications, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInChurchDedications Context triple: [San Juan, usedInChurchDedications, yes]
-
A.
liturgicalDedication
Indicates that something (typically a religious building, object, or time) is formally dedicated or consecrated for use in a specific liturgical or worship context.
-
B.
celebratedInChurch
Indicates that a ceremony, event, or occasion is formally observed or performed within a church setting.
-
C.
hasParishChurchDedication
chosen
Indicates that a parish church is dedicated to, or placed under the patronage of, a particular figure, saint, or sacred concept.
-
D.
usedAsChurchUntil
Indicates that something served the function or role of a church up to a specified point in time.
-
E.
usedAsChurchFrom
Indicates that something functioned or was utilized as a church starting from a specified point in time.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 28, 2026, 12:06 p.m.