Triple
T3421943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parma Cathedral |
E72132
|
entity |
| Predicate | hasBellTowerPosition |
P2495
|
FINISHED |
| Object | adjacent to the cathedral |
—
|
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: adjacent to the cathedral | Statement: [Parma Cathedral, hasBellTowerPosition, adjacent to the cathedral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBellTowerPosition Context triple: [Parma Cathedral, hasBellTowerPosition, adjacent to the cathedral]
-
A.
hasBellTower
chosen
Indicates that one entity (typically a building or structure) possesses or includes a bell tower as part of it.
-
B.
hasClockTower
Indicates that one entity possesses or features a clock tower as part of its structure or property.
-
C.
hasTower
Indicates that one entity possesses, contains, or is characterized by the presence of a tower.
-
D.
isObservationTower
Indicates that something functions as an observation tower, serving primarily as a structure for viewing or monitoring an area from an elevated position.
-
E.
hasObservationDeckAccess
Indicates that an entity is permitted to enter or use an observation deck.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb950f65481908c4aad15516e7a7c |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.