Triple
T15115333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockport, Washington |
E361020
|
entity |
| Predicate | hasNearbyWildlifeViewing |
P104210
|
FINISHED |
| Object | bald eagles on the Skagit River |
—
|
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: bald eagles on the Skagit River | Statement: [Rockport, Washington, hasNearbyWildlifeViewing, bald eagles on the Skagit River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyWildlifeViewing Context triple: [Rockport, Washington, hasNearbyWildlifeViewing, bald eagles on the Skagit River]
-
A.
hasNearbyWildlife
Indicates that there is wildlife located close to or in the immediate vicinity of the referenced entity.
-
B.
hasWildlifeObservationPoints
chosen
Indicates that a location or area includes designated points or spots where wildlife can be observed.
-
C.
hasWildlifeActivity
Indicates that wildlife is present in the area and engaging in observable behaviors or movements.
-
D.
hasNearbyWildlifeRefuge
Indicates that something is located close to or in the vicinity of a designated wildlife refuge.
-
E.
hasWildlifeSite
Indicates that a location or entity possesses, contains, or is designated as a wildlife site.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0058f4fb88190a3d446a466aebcf1 |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:05 a.m.