Triple
T18899014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hat Head headland lookout |
E462286
|
entity |
| Predicate | typicalWildlifeSighted |
P111243
|
FINISHED |
| Object | humpback whales |
—
|
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: humpback whales | Statement: [Hat Head headland lookout, typicalWildlifeSighted, humpback whales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWildlifeSighted Context triple: [Hat Head headland lookout, typicalWildlifeSighted, humpback whales]
-
A.
typicalWildlifeObserved
chosen
Indicates that certain wildlife species are commonly or characteristically observed in a given area or context.
-
B.
hasNearbyWildlife
Indicates that there is wildlife located close to or in the immediate vicinity of the referenced entity.
-
C.
possibleSightings
Indicates that there are reported or potential observations of one entity by another or at a particular place or time.
-
D.
wildlifeInteractionType
Indicates the type or nature of interaction occurring between wildlife and another entity (such as humans, other animals, or the environment).
-
E.
hasWildlifeActivity
Indicates that wildlife is present in the area and engaging in observable behaviors or movements.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c5277d788190a565794f7bd0e608 |
completed | April 20, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.