Triple
T36189227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea eagle safaris |
E1046939
|
entity |
| Predicate | involvesAnimalObservation |
P180838
|
FINISHED |
| Object | sea eagles |
—
|
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: sea eagles | Statement: [Sea eagle safaris, involvesAnimalObservation, sea eagles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesAnimalObservation Context triple: [Sea eagle safaris, involvesAnimalObservation, sea eagles]
-
A.
hasWildlifeObservation
chosen
Indicates that a wildlife observation event or record is associated with a particular entity (such as a location, time, or observer).
-
B.
typicalWildlifeObserved
Indicates that certain wildlife species are commonly or characteristically observed in a given area or context.
-
C.
observationType
Indicates the specific kind or category of observation being made or recorded in a given context.
-
D.
birdwatchingFeature
Indicates a feature, characteristic, or amenity that is specifically related to or beneficial for birdwatching activities.
-
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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: May 3, 2026, 4:08 p.m.