Triple
T4842147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cardinal-Priest of San Crisogono |
E108202
|
entity |
| Predicate | linkedToChurch |
P13041
|
FINISHED |
| Object | titular church |
—
|
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: titular church | Statement: [Cardinal-Priest of San Crisogono, linkedToChurch, titular church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToChurch Context triple: [Cardinal-Priest of San Crisogono, linkedToChurch, titular church]
-
A.
associatedWithChurch
chosen
Indicates a relationship in which an entity has a connection, involvement, or affiliation with a church.
-
B.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
-
C.
linkedDiocese
Indicates a formal association or connection established between one diocese and another.
-
D.
hasParentChurch
Indicates that a church or religious organization is institutionally subordinate to or derived from another church, which serves as its parent or overseeing body.
-
E.
sharesTempleChurchWith
Indicates that two entities use or are associated with the same building or site that functions as both a temple and a church.
- 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_69bd4409b264819085ab855f3eb5381a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e01872c81909607010c10538ad1 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2375a4819098e16acb982c8fab |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.