Triple
T29085861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia de Odeceixe |
E734109
|
entity |
| Predicate | hasUsageSeason |
P150429
|
FINISHED |
| Object | most popular in summer months |
—
|
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: most popular in summer months | Statement: [Praia de Odeceixe, hasUsageSeason, most popular in summer months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUsageSeason Context triple: [Praia de Odeceixe, hasUsageSeason, most popular in summer months]
-
A.
hasUseSeason
chosen
Indicates the season or time of year during which something is intended or suitable to be used.
-
B.
usedInSeason
Indicates that something (such as an item, strategy, or element) is utilized or appears within a particular season.
-
C.
hasSeason
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
-
D.
hasSeasonType
Indicates that something is associated with a particular category or type of season (e.g., summer, winter, rainy).
-
E.
usedForSeasonRange
Indicates the span of seasons or time period during which something is intended or suitable to be used.
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 11 a.m.