Triple
T695438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tavira |
E13884
|
entity |
| Predicate | hasBeach |
P1922
|
FINISHED |
| Object | Praia de Tavira |
E13884
|
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: Praia de Tavira | Statement: [Tavira, hasBeach, Praia de Tavira]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Praia de Tavira Context triple: [Tavira, hasBeach, Praia de Tavira]
-
A.
Olhão
Olhão is a coastal city in Portugal’s Algarve region, known for its fishing port, historic waterfront, and access to the Ria Formosa lagoon and nearby islands.
-
B.
Tavira
chosen
Tavira is a historic coastal town in Portugal’s Algarve region, known for its picturesque old town, Roman bridge, and nearby island beaches.
-
C.
Albufeira
Albufeira is a popular coastal resort city in Portugal’s Algarve region, known for its beaches, nightlife, and tourism.
-
D.
Praia da Oura
Praia da Oura is a popular sandy beach in Portugal’s Algarve region, known for its lively atmosphere, golden cliffs, and proximity to the resort town of Albufeira.
-
E.
Praia da Falésia
Praia da Falésia is a famous Algarve beach in southern Portugal, known for its long stretch of golden sand backed by striking red and white cliffs.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0c5f51c8190acc4915099e4b384 |
completed | March 1, 2026, 8:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a66d9140148190a439ac7a03ee88b2 |
completed | March 3, 2026, 5:11 a.m. |
Created at: March 1, 2026, 7:36 p.m.