Triple
T6183229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zadar Cathedral |
E137992
|
entity |
| Predicate | hasTowerLocation |
P42882
|
FINISHED |
| Object | adjacent to the west front |
—
|
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 west front | Statement: [Zadar Cathedral, hasTowerLocation, adjacent to the west front]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTowerLocation Context triple: [Zadar Cathedral, hasTowerLocation, adjacent to the west front]
-
A.
hasTowerPosition
Indicates that an entity occupies or is assigned a specific position or location within a tower.
-
B.
hasTower
Indicates that one entity possesses, contains, or is characterized by the presence of a tower.
-
C.
hasTowerHeight
Indicates that an entity (such as a tower or structure) has a specific height value associated with it.
-
D.
hasBuildingLocation
chosen
Indicates that a building is situated at, or associated with, a specific geographic or spatial location.
-
E.
isObservationTower
Indicates that something functions as an observation tower, serving primarily as a structure for viewing or monitoring an area from an elevated position.
- 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_69c008a8fd408190b7ec6e42934974a6 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06100c2b0819097f287e86f63d590 |
completed | March 22, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:19 p.m.