Triple
T19986770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woolgoolga Headland |
E493951
|
entity |
| Predicate | typicalWhaleWatchingSeason |
P120264
|
FINISHED |
| Object | June to November |
—
|
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: June to November | Statement: [Woolgoolga Headland, typicalWhaleWatchingSeason, June to November]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWhaleWatchingSeason Context triple: [Woolgoolga Headland, typicalWhaleWatchingSeason, June to November]
-
A.
bestKnownSeasonForWhales
Indicates the season during which whales are most commonly or prominently observed in a given context.
-
B.
typicalSeasonTiming
Indicates the usual time period or season during which something normally occurs or is expected to take place.
-
C.
hasWildlifeViewingSeason
chosen
Indicates that there is a specific time period during which wildlife can be observed or viewed in relation to the subject.
-
D.
navigationSeason
Indicates the time period or season during which navigation or travel along a route or waterway is possible or permitted.
-
E.
typicalStartSeason
Indicates the season during which something (such as an activity, event, or phenomenon) usually begins.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d16f60c81909ba02c0a3429ecae |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:29 p.m.