Triple
T6407212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moose River, Maine |
E127613
|
entity |
| Predicate | hasSeasonalTourism |
P53625
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Moose River, Maine, hasSeasonalTourism, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonalTourism Context triple: [Moose River, Maine, hasSeasonalTourism, yes]
-
A.
seasonalTourism
chosen
Indicates that tourism activity in a place varies significantly by season, with distinct peak and off-peak periods.
-
B.
hasTouristVisits
Indicates that one entity experiences or records visits from tourists to another entity.
-
C.
hasSeasonalEvents
Indicates that an entity organizes or experiences events that occur only during specific seasons or times of the year.
-
D.
hasTourismFunction
Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
-
E.
hasTourismIndustry
Indicates that a place or region possesses an established tourism industry, involving organized services and activities catering to visitors and travelers.
- 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068b3541c8190be89b24b313d7300 |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f40ecc8190b1df17b96767675c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:41 p.m.