Triple
T32895500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia da Angrinha |
E841459
|
entity |
| Predicate | hasBeachCategory |
P183749
|
FINISHED |
| Object | urban-adjacent beach |
—
|
LITERAL 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: urban-adjacent beach | Statement: [Praia da Angrinha, hasBeachCategory, urban-adjacent beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeachCategory Context triple: [Praia da Angrinha, hasBeachCategory, urban-adjacent beach]
-
A.
hasBeachCharacteristic
Indicates that something possesses a specific quality, feature, or attribute associated with a beach.
-
B.
hasBeach
Indicates that one entity possesses, includes, or is characterized by a beach as part of its features or environment.
-
C.
hasBeachSection
Indicates that an area, location, or property includes or is associated with a specific section designated as a beach.
-
D.
hasBeachTagRequirement
Indicates that something is subject to a specific requirement or condition related to beach access, use, or tagging.
-
E.
hasBeachDestination
Indicates that a place is a destination characterized by having a beach suitable for visits or recreation.
- F. None of above. chosen
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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a224365081908ff6958e3b30bd05 |
completed | May 3, 2026, 7:29 p.m. |
Created at: May 1, 2026, 1:18 a.m.