Triple
T34915458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nossob tourist routes |
E1006986
|
entity |
| Predicate | bestTimeForWildlifeViewing |
P79541
|
FINISHED |
| Object | early morning |
—
|
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: early morning | Statement: [Nossob tourist routes, bestTimeForWildlifeViewing, early morning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestTimeForWildlifeViewing Context triple: [Nossob tourist routes, bestTimeForWildlifeViewing, early morning]
-
A.
bestTimeToVisitForWildlife
chosen
Indicates the most favorable time period to visit a place specifically for observing wildlife activity or diversity.
-
B.
hasWildlifeViewingSeason
Indicates that there is a specific time period during which wildlife can be observed or viewed in relation to the subject.
-
C.
hasWildlifeObservationPoints
Indicates that a location or area includes designated points or spots where wildlife can be observed.
-
D.
typicalWildlifeObserved
Indicates that certain wildlife species are commonly or characteristically observed in a given area or context.
-
E.
birdwatchingFeature
Indicates a feature, characteristic, or amenity that is specifically related to or beneficial for birdwatching activities.
- 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.