Triple
T31427829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melk |
E801715
|
entity |
| Predicate | nearbySiteUNESCOStatus |
P16759
|
FINISHED |
| Object | UNESCO World Heritage Site |
E1331
|
NE 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: UNESCO World Heritage Site | Statement: [Melk, nearbySiteUNESCOStatus, UNESCO World Heritage Site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbySiteUNESCOStatus Context triple: [Melk, nearbySiteUNESCOStatus, UNESCO World Heritage Site]
-
A.
nearbyWorldHeritageSite
chosen
Indicates that one entity is located close to, or in the immediate vicinity of, a designated World Heritage Site.
-
B.
heritageSiteTypeNearby
Indicates that a particular type of heritage site is located in close proximity to the referenced entity.
-
C.
UNESCOWorldHeritageSiteRelated
Indicates a relationship where one entity is designated as, part of, or otherwise officially associated with a UNESCO World Heritage Site.
-
D.
hasUNESCOCandidateSite
Indicates that an entity possesses or includes at least one site that is a candidate for inscription on the UNESCO World Heritage List.
-
E.
nearbyProtectedSite
Indicates that one entity is located close to a protected site, such as a reserve, park, or conservation area.
- F. None of above.
Provenance (4 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b0774af0c81908aec108aefc58ee5 |
completed | June 11, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: April 30, 2026, 8:54 p.m.