Triple
T18485387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirounga angustirostris |
E451674
|
entity |
| Predicate | historicallyOverexploitedFor |
P131849
|
FINISHED |
| Object | blubber |
—
|
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: blubber | Statement: [Mirounga angustirostris, historicallyOverexploitedFor, blubber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyOverexploitedFor Context triple: [Mirounga angustirostris, historicallyOverexploitedFor, blubber]
-
A.
historicallyFishedBy
Indicates that an area or body of water has been used for fishing by a particular entity or group in the past.
-
B.
isEndangeredDueTo
Indicates that an entity is endangered as a result of the specific cause or factor represented by the related entity.
-
C.
hasExtinctSpecies
Indicates that at least one species associated with the subject entity is no longer extant (i.e., has gone extinct).
-
D.
wasOnceNearExtinction
Indicates that the entity’s population or existence was at one time so low or threatened that it was in serious danger of disappearing entirely.
-
E.
extinctionReason
Indicates the cause or factor responsible for an entity’s extinction.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531d6502c8190af167b954bf8e989 |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:35 a.m.