Triple
T30182477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Rauma |
E767238
|
entity |
| Predicate | hasWorldHeritageRegion |
P10482
|
FINISHED |
| Object | Europe and North America |
—
|
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: Europe and North America | Statement: [Old Rauma, hasWorldHeritageRegion, Europe and North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorldHeritageRegion Context triple: [Old Rauma, hasWorldHeritageRegion, Europe and North America]
-
A.
hasWorldHeritageSite
Indicates that a location or entity possesses or contains a site designated as a UNESCO World Heritage Site.
-
B.
hasWorldHeritageContext
Indicates that something is associated with, relevant to, or situated within the context of a UNESCO World Heritage site or designation.
-
C.
UNESCOWorldHeritageAreaHa
Indicates that an area is designated as a UNESCO World Heritage site and specifies its size in hectares.
-
D.
UNESCOWorldHeritageSiteWithin
chosen
Indicates that a UNESCO World Heritage Site is geographically located within the boundaries of a specified area or region.
-
E.
hasHeritageRegion
Indicates that an entity is associated with, originates from, or is culturally linked to a specific heritage region.
- 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_69f2247cc3d88190811dec3face94bf5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:26 p.m.