Triple
T30757421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Maria della Consolazione |
E783126
|
entity |
| Predicate | hasGreekCrossPlan |
P176757
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Santa Maria della Consolazione, hasGreekCrossPlan, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGreekCrossPlan Context triple: [Santa Maria della Consolazione, hasGreekCrossPlan, true]
-
A.
hasCross
Indicates that one entity possesses, displays, or is marked by a cross in relation to another entity or context.
-
B.
isGreekCatholic
Indicates that an entity belongs to or is associated with the Greek Catholic (Byzantine Rite, in communion with Rome) religious tradition.
-
C.
hasGreekCounterpartGroup
Indicates that something is associated with a corresponding group or set of counterparts in the context of Greek tradition or classification.
-
D.
usesGreekLetterSystem
Indicates that one entity employs a writing, naming, or notation system based on Greek letters in relation to another entity or context.
-
E.
hasGreekLife
Indicates that an institution or organization offers or supports Greek-letter fraternities and/or sororities.
- F. None of above. chosen
Provenance (4 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e60109648190947a64ca4ce81a3a |
completed | May 3, 2026, 6:06 a.m. |
Created at: April 29, 2026, 8:39 p.m.