Triple
T33159768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beira Baixa |
E848692
|
entity |
| Predicate | hasUNESCOStatusNearby |
P16759
|
FINISHED |
| Object | Alto Douro Wine Region |
—
|
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: Alto Douro Wine Region | Statement: [Beira Baixa, hasUNESCOStatusNearby, Alto Douro Wine Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUNESCOStatusNearby Context triple: [Beira Baixa, hasUNESCOStatusNearby, Alto Douro Wine Region]
-
A.
nearbyWorldHeritageSite
chosen
Indicates that one entity is located close to, or in the immediate vicinity of, a designated World Heritage Site.
-
B.
hasUNESCOCandidateSite
Indicates that an entity possesses or includes at least one site that is a candidate for inscription on the UNESCO World Heritage List.
-
C.
hasNearbyPilgrimageSite
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
-
D.
nearbyProtectedSite
Indicates that one entity is located close to a protected site, such as a reserve, park, or conservation area.
-
E.
hasUNESCOIdNote
Indicates that there is a note or annotation associated with an entity’s UNESCO identifier.
- 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_69f3495b02d08190bb3d366823dffc21 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 1, 2026, 1:28 a.m.