Triple
T4542621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | northern elephant seal |
E107569
|
entity |
| Predicate | restBehaviorAtSea |
P49505
|
FINISHED |
| Object | sleep during drift dives |
—
|
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: sleep during drift dives | Statement: [northern elephant seal, restBehaviorAtSea, sleep during drift dives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restBehaviorAtSea Context triple: [northern elephant seal, restBehaviorAtSea, sleep during drift dives]
-
A.
usesAtSea
Indicates that something is employed, operated, or applied in a maritime or oceanic environment.
-
B.
isAbandonedAtSeaBy
Indicates that one entity is deliberately left behind or deserted at sea by another entity.
-
C.
maritimeActivity
chosen
Indicates activities, operations, or behaviors that take place at sea or are directly related to maritime environments and navigation.
-
D.
sailingUnder
Indicates that one entity (typically a vessel) is operating or traveling while registered, flagged, or officially recognized under the authority or jurisdiction of another entity (such as a country or organization).
-
E.
endSea
Indicates that something marks the boundary or termination point of a sea or sea 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_69bd43f922788190b7edfa294e39b178 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57d3be988190bf118c4a87415613 |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:04 p.m.