Triple
T32833832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mänttä-Vilppula |
E839769
|
entity |
| Predicate | hasIndustrialHeritageIn |
P2411
|
FINISHED |
| Object | paper industry |
—
|
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: paper industry | Statement: [Mänttä-Vilppula, hasIndustrialHeritageIn, paper industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndustrialHeritageIn Context triple: [Mänttä-Vilppula, hasIndustrialHeritageIn, paper industry]
-
A.
hasIndustrialHeritage
chosen
Indicates that an entity possesses or is associated with historically significant industrial sites, structures, or practices.
-
B.
nearbyIndustrialHistory
Indicates that an entity is located close to a site, feature, or area of industrial historical significance.
-
C.
hasIndustrialTown
Indicates that an entity possesses or is associated with a town characterized primarily by industrial activities or facilities.
-
D.
hasIndustrialSiteIn
Indicates that an entity possesses, operates, or is responsible for an industrial facility located within a specified place or area.
-
E.
hasHistoricSite
Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
- 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
Created at: May 1, 2026, 1:16 a.m.