Triple
T32507589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caribbean monk seal |
E830840
|
entity |
| Predicate | lastConfirmedSightingYear |
P160406
|
FINISHED |
| Object | 1952 |
—
|
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: 1952 | Statement: [Caribbean monk seal, lastConfirmedSightingYear, 1952]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastConfirmedSightingYear Context triple: [Caribbean monk seal, lastConfirmedSightingYear, 1952]
-
A.
lastKnownWildSightingYear
chosen
Indicates the calendar year in which the entity was most recently observed living in the wild.
-
B.
lastConfirmedSightingLocation
Indicates the most recent location where the entity was reliably observed or reported.
-
C.
lastCaptiveIndividualDiedYear
Indicates the calendar year in which the final surviving captive individual of a given group or species died.
-
D.
wasFirstObservedIn
Indicates that an entity was initially noticed, recorded, or detected at a particular time or place.
-
E.
lastKnownWildRecords
Indicates the most recent documented instances of a species or entity observed in the wild before it disappeared or became otherwise unrecorded in natural conditions.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c44bf4d481909a401bf086d57bb6 |
completed | May 3, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1 a.m.