Triple
T30011152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inowrocław County |
E762462
|
entity |
| Predicate | hasSaltHeritageSite |
P27481
|
FINISHED |
| Object | Inowrocław saltworks |
—
|
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: Inowrocław saltworks | Statement: [Inowrocław County, hasSaltHeritageSite, Inowrocław saltworks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSaltHeritageSite Context triple: [Inowrocław County, hasSaltHeritageSite, Inowrocław saltworks]
-
A.
hasHeritageOfSite
Indicates that a site possesses or is associated with a particular heritage designation, tradition, or cultural-historical value.
-
B.
hasHeritageFeature
chosen
Indicates that an entity possesses or includes a feature recognized as part of cultural, historical, or natural heritage.
-
C.
hasHeritageValueFor
Indicates that something possesses cultural, historical, or heritage significance for a particular entity or community.
-
D.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
E.
hasHeritageElements
Indicates that something contains or includes elements that are part of a cultural, historical, or natural heritage.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 29, 2026, 6:44 p.m.