Triple
T23661975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelsö parish |
E584472
|
entity |
| Predicate | hasNotableSiteNearby |
P19575
|
FINISHED |
| Object | UNESCO World Heritage Site Birka and Hovgården |
—
|
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: UNESCO World Heritage Site Birka and Hovgården | Statement: [Adelsö parish, hasNotableSiteNearby, UNESCO World Heritage Site Birka and Hovgården]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSiteNearby Context triple: [Adelsö parish, hasNotableSiteNearby, UNESCO World Heritage Site Birka and Hovgården]
-
A.
notableNearbySite
chosen
Indicates that one entity is a significant or noteworthy site located close to another entity.
-
B.
hasNearbyPilgrimageSite
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
-
C.
hasAttractionNearby
Indicates that one entity is located close to another entity that serves as an attraction or point of interest.
-
D.
hasNaturalParkNearby
Indicates that one entity is located close to, or in the vicinity of, a natural park associated with the other entity.
-
E.
hasNearbyStatePark
Indicates that a location is situated close to at least one designated state park.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4094c448190be12402422451e89 |
completed | April 29, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.