Triple
T13705048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Harbour |
E328617
|
entity |
| Predicate | typicalWildlifeObserved |
P111243
|
FINISHED |
| Object | southern right 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: southern right whales | Statement: [Old Harbour, typicalWildlifeObserved, southern right whales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWildlifeObserved Context triple: [Old Harbour, typicalWildlifeObserved, southern right whales]
-
A.
hasNearbyWildlife
Indicates that there is wildlife located close to or in the immediate vicinity of the referenced entity.
-
B.
hasWildlifeActivity
Indicates that wildlife is present in the area and engaging in observable behaviors or movements.
-
C.
wildlifeInteractionType
Indicates the type or nature of interaction occurring between wildlife and another entity (such as humans, other animals, or the environment).
-
D.
typicalTargetSpecies
Indicates the species that is most commonly or characteristically targeted or affected by a given action, process, or agent.
-
E.
hasWildlifeObservationPoints
Indicates that a location or area includes designated points or spots where wildlife can be observed.
- F. None of above. chosen
Provenance (4 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dcad17732c8190bbd0d73107711c99 |
completed | April 13, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:54 p.m.