Triple
T16424984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sombor |
E398918
|
entity |
| Predicate | hasCulturalAssetType |
P47444
|
FINISHED |
| Object | historic buildings |
—
|
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: historic buildings | Statement: [Sombor, hasCulturalAssetType, historic buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCulturalAssetType Context triple: [Sombor, hasCulturalAssetType, historic buildings]
-
A.
hasCulturalProduct
Indicates that an entity possesses, produces, or is associated with a cultural artifact, work, or output (such as art, literature, music, or media).
-
B.
hasCulturalProperty
Indicates that something possesses or is associated with a cultural attribute, value, or characteristic.
-
C.
hasCulturalIcon
Indicates that an entity is associated with or possesses a person, symbol, or object widely recognized as a significant representation of a particular culture.
-
D.
hasCulturalSiteType
chosen
Indicates that an entity is associated with, or classified by, a specific type or category of cultural site.
-
E.
hasCulturalFacilityType
Indicates that an entity has or is associated with a specific type of cultural facility (such as a museum, theater, or gallery).
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328f9da9081908dadbdac4b2d38ec |
completed | April 18, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.