Triple
T29753256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vorarlberg Museum |
E752959
|
entity |
| Predicate | mainBuildingLocatedOn |
P42882
|
FINISHED |
| Object | Bregenz lakeside area |
—
|
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: Bregenz lakeside area | Statement: [Vorarlberg Museum, mainBuildingLocatedOn, Bregenz lakeside area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainBuildingLocatedOn Context triple: [Vorarlberg Museum, mainBuildingLocatedOn, Bregenz lakeside area]
-
A.
locatedOnBuilding
Indicates that one entity is physically situated on the exterior or rooftop surface of a building.
-
B.
seatBuildingLocatedIn
Indicates that the building serving as a seat (e.g., headquarters or main office) is geographically located within a specified area or place.
-
C.
mainBuildingName
Indicates the name that is designated as the primary or main building associated with an entity.
-
D.
isMainBuildingOf
Indicates that a building serves as the primary or central facility associated with a particular organization, complex, or site.
-
E.
hasBuildingLocation
chosen
Indicates that a building is situated at, or associated with, a specific geographic or spatial location.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f673c8c00881908596a9e9fca49436 |
completed | May 2, 2026, 9:59 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:55 p.m.