Triple
T26135196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karpniki |
E659358
|
entity |
| Predicate | hasBuildingUseAt |
P147436
|
FINISHED |
| Object | Karpniki Palace, hotel and conference center |
—
|
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: Karpniki Palace, hotel and conference center | Statement: [Karpniki, hasBuildingUseAt, Karpniki Palace, hotel and conference center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingUseAt Context triple: [Karpniki, hasBuildingUseAt, Karpniki Palace, hotel and conference center]
-
A.
currentBuildingUse
chosen
Indicates the present functional purpose or activity for which a building is being used.
-
B.
buildingUsedSince
Indicates that a particular building has been in use starting from a specified point in time.
-
C.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
D.
hasFloorUse
Indicates that a particular floor or level of a building is designated for a specific function, activity, or type of use.
-
E.
hasSiteUse
Indicates that a site is used or designated for a particular function, activity, or purpose.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 26, 2026, 8:17 p.m.