Triple
T18639182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pico da Bandeira |
E455635
|
entity |
| Predicate | hasCampingAreaNearby |
P79315
|
FINISHED |
| Object | Terreirão camping area |
—
|
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: Terreirão camping area | Statement: [Pico da Bandeira, hasCampingAreaNearby, Terreirão camping area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampingAreaNearby Context triple: [Pico da Bandeira, hasCampingAreaNearby, Terreirão camping area]
-
A.
hasCampground
Indicates that one entity provides, contains, or is associated with a campground facility or area for another entity.
-
B.
hasCampingOption
Indicates that an entity offers or includes the possibility to camp (e.g., designated camping facilities or areas).
-
C.
nearbyCampground
chosen
Indicates that one location has a campground situated close to it in geographic proximity.
-
D.
hasRecreationalUseNearby
Indicates that there is at least one location or facility for recreational activities situated close to the referenced entity.
-
E.
hasCampingPolicy
Indicates that an entity specifies rules, restrictions, or guidelines regarding camping activities on its premises or within its jurisdiction.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fcac2d48190a15ce8cc8e175198 |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.