Triple
T31651827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia do Inatel |
E807748
|
entity |
| Predicate | hasRegionTourismDesignation |
P59632
|
FINISHED |
| Object | Algarve tourist 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: Algarve tourist region | Statement: [Praia do Inatel, hasRegionTourismDesignation, Algarve tourist region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionTourismDesignation Context triple: [Praia do Inatel, hasRegionTourismDesignation, Algarve tourist region]
-
A.
touristDesignation
Indicates that a place or entity has been formally identified or labeled as a tourist attraction or destination.
-
B.
hasRegionDesignation
chosen
Indicates that an entity is assigned or associated with a specific regional classification or designation.
-
C.
religiousDesignation
Indicates the specific religious role, status, or affiliation assigned to an entity.
-
D.
stateDesignation
Indicates that an entity has been formally assigned or recognized with a particular status, title, or classification by an official authority or governing body.
-
E.
earthDesignation
Indicates that an entity has a specific name or label assigned to it for use in an Earth-based or human-centric context.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a0189f3f0248190a1b018164d18e6f5 |
completed | May 11, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_6a0187ee0920819097047bb55e1f9506 |
completed | May 11, 2026, 7:40 a.m. |
Created at: April 30, 2026, 10:53 p.m.