Triple
T19031501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Cathedral of San Fernando |
E465749
|
entity |
| Predicate | originalParishEstablishmentDate |
P46988
|
FINISHED |
| Object | 1754 |
—
|
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: 1754 | Statement: [Metropolitan Cathedral of San Fernando, originalParishEstablishmentDate, 1754]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalParishEstablishmentDate Context triple: [Metropolitan Cathedral of San Fernando, originalParishEstablishmentDate, 1754]
-
A.
parishEstablished
chosen
Indicates that a parish was formally created or founded at a specific time or under specific authority.
-
B.
parishFoundedBy
Indicates that a parish was established or created by a specific person or organization.
-
C.
firstOrdinariateErectedDate
Indicates the date on which the first ordinariate was formally established.
-
D.
municipalityEstablished
Indicates that a municipality was officially created or founded at a specific point in time.
-
E.
isHistoricParishOf
Indicates that one entity is a historic parish that formerly served, or is recognized as having served, as the parish jurisdiction for another entity.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d7404d748190bcb51692fb822fd4 |
completed | April 20, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69e4a3001e388190aa6057266514e75a |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.