Triple
T29496780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia do Orzán |
E748249
|
entity |
| Predicate | hasSeasonalCrowds |
P127382
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Praia do Orzán, hasSeasonalCrowds, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonalCrowds Context triple: [Praia do Orzán, hasSeasonalCrowds, true]
-
A.
hasPeakVisitationSeason
chosen
Indicates that an entity experiences its highest or most concentrated level of visitation during a specific season or time period.
-
B.
isSeasonalAttraction
Indicates that an attraction is available or prominently featured only during specific seasons or times of the year.
-
C.
hasSeasonalEvents
Indicates that an entity organizes or experiences events that occur only during specific seasons or times of the year.
-
D.
hasSeasonalRidershipPeak
Indicates that the ridership of an entity (such as a service or route) reaches its highest levels during specific seasons or times of the year.
-
E.
typicalVisitorsPerSeason
Indicates the usual number of visitors associated with each season for a given entity or location.
- 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_69f0bd448c6881908aa6b475cefd5ddc |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: April 28, 2026, 4:19 p.m.