Triple
T3492084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antarctic fur seal |
E73755
|
entity |
| Predicate | nearExtinction |
P19126
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Antarctic fur seal, nearExtinction, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearExtinction Context triple: [Antarctic fur seal, nearExtinction, early 20th century]
-
A.
wasOnceNearExtinction
chosen
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.
-
B.
thoughtExtinct
Indicates that something was previously believed to no longer exist or to have died out, but is now recognized or suggested to still exist.
-
C.
extinctionReason
Indicates the cause or factor responsible for an entity’s extinction.
-
D.
extinctionType
Indicates the specific manner or category by which an entity ceases to exist or becomes extinct.
-
E.
extinct
Indicates that the referenced entity no longer exists as a living or active member of its former kind or category.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbabd1708190b1ca4cbc87462b5b |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0b34908190b2bb5766a2231f7a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.