Triple
T26550671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Padua Cathedral |
E671668
|
entity |
| Predicate | mainCityChurchOf |
P41348
|
FINISHED |
| Object | Padua |
—
|
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: Padua | Statement: [Padua Cathedral, mainCityChurchOf, Padua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCityChurchOf Context triple: [Padua Cathedral, mainCityChurchOf, Padua]
-
A.
principalChurchOf
Indicates that one church serves as the main or most important church associated with a particular entity, such as a region, denomination, or institution.
-
B.
hasMainCathedral
Indicates that an entity possesses or is associated with a primary cathedral that serves as its main ecclesiastical center.
-
C.
motherChurch
Indicates that one church serves as the primary, founding, or supervising church in relation to another church.
-
D.
wasCityChurchOf
chosen
Indicates that a given church functioned as the principal or designated city church for a particular city.
-
E.
isMetropolitanChurch
Indicates that a church holds metropolitan status, serving as the principal ecclesiastical authority over other churches within a defined region or province.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 1:47 a.m.