Triple
T8093191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Simeon, California |
E188917
|
entity |
| Predicate | hasWildlifeViewing |
P34896
|
FINISHED |
| Object | northern elephant seals |
—
|
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: northern elephant seals | Statement: [San Simeon, California, hasWildlifeViewing, northern elephant seals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWildlifeViewing Context triple: [San Simeon, California, hasWildlifeViewing, northern elephant seals]
-
A.
hasWildlifeAccess
Indicates that an entity has the ability, permission, or physical means to reach or interact with wildlife or wildlife habitats.
-
B.
hasNearbyWildlife
chosen
Indicates that there is wildlife located close to or in the immediate vicinity of the referenced entity.
-
C.
hasWildlifeIssue
Indicates that an entity is affected by, involved in, or responsible for a problem or conflict related to wildlife.
-
D.
hasWildlifeStatus
Indicates the conservation or protection status assigned to wildlife associated with an entity.
-
E.
hasWildernessArea
Indicates that one entity possesses, contains, or is associated with a designated wilderness area.
- 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_69ca82b7b3e88190b9041ab0ef28b3cb |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4222b68c81909c8bc326763240d0 |
completed | March 31, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:30 p.m.