Triple
T25074317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Trieste |
E628004
|
entity |
| Predicate | hasHistoricCathedral |
P108426
|
FINISHED |
| Object | San Giusto |
—
|
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: San Giusto | Statement: [Diocese of Trieste, hasHistoricCathedral, San Giusto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricCathedral Context triple: [Diocese of Trieste, hasHistoricCathedral, San Giusto]
-
A.
hasCathedralTown
Indicates that a given town is recognized as having a cathedral, typically serving as the seat of a bishop or central church authority.
-
B.
hasHistoricChurches
Indicates that an entity possesses or contains one or more churches of recognized historical significance.
-
C.
hasCathedralStatusSince
Indicates the point in time from which something has held the official status of a cathedral.
-
D.
hasCathedralCity
Indicates that a particular city is officially recognized as the cathedral city associated with a given ecclesiastical jurisdiction or region.
-
E.
hasCatholicCathedral
chosen
Indicates that a place or jurisdiction possesses at least one officially recognized Catholic cathedral within its boundaries.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 18, 2026, 6:20 a.m.