Triple
T32942290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Škoda Auto Museum |
E842702
|
entity |
| Predicate | locatedInBuildingOf |
P166606
|
FINISHED |
| Object | former Škoda factory premises |
—
|
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: former Škoda factory premises | Statement: [Škoda Auto Museum, locatedInBuildingOf, former Škoda factory premises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInBuildingOf Context triple: [Škoda Auto Museum, locatedInBuildingOf, former Škoda factory premises]
-
A.
locatedInBuildingUsedAs
Indicates that something is located inside a building that is being used for a specified purpose or function.
-
B.
locatedOnBuilding
Indicates that one entity is physically situated on the exterior or rooftop surface of a building.
-
C.
isLocatedInBuilding
chosen
Indicates that one entity is physically situated within or inside the structure of a particular building.
-
D.
locatedInBuildingOwnedBy
Indicates that one entity is situated within a building that is owned by another entity.
-
E.
locatedInBuildingWithFeature
Indicates that something is located in a building that possesses a specified feature or characteristic.
- 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a03433dd64c8190ab620709153b6278 |
completed | May 12, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_6a034107e53881909127bac98cac3429 |
completed | May 12, 2026, 3:02 p.m. |
Created at: May 1, 2026, 1:20 a.m.