Triple
T37154107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petrov Hill |
E920445
|
entity |
| Predicate | hasBuildingOnTop |
P91879
|
FINISHED |
| Object | Cathedral of St. Peter and Paul |
—
|
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: Cathedral of St. Peter and Paul | Statement: [Petrov Hill, hasBuildingOnTop, Cathedral of St. Peter and Paul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingOnTop Context triple: [Petrov Hill, hasBuildingOnTop, Cathedral of St. Peter and Paul]
-
A.
hasTopConstruction
Indicates that one entity serves as the uppermost structural element or construction positioned on top of another entity.
-
B.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
C.
hasBuildingFrom
Indicates a relationship where a location or site possesses or includes a building that originates from, or was constructed in, a specified time period, source, or context.
-
D.
hasRooftopStructure
Indicates that one entity possesses or features a structural element located on its roof.
-
E.
hasSurfaceBuilding
chosen
Indicates that one entity possesses or is associated with a building located on its surface.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:15 p.m.