Triple
T23525997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yakov Sannikov |
E576433
|
entity |
| Predicate | reportedObservation |
P36943
|
FINISHED |
| Object | land mass north of Kotelny Island |
—
|
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: land mass north of Kotelny Island | Statement: [Yakov Sannikov, reportedObservation, land mass north of Kotelny Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportedObservation Context triple: [Yakov Sannikov, reportedObservation, land mass north of Kotelny Island]
-
A.
observationNote
Indicates that there is an associated free-text comment or remark providing additional details or context about an observation.
-
B.
observation
chosen
Indicates that one entity perceives, monitors, or takes note of another entity or phenomenon, typically to gather information about it.
-
C.
observationType
Indicates the specific kind or category of observation being made or recorded in a given context.
-
D.
basedOnObservationOf
Indicates that something is derived from, justified by, or determined using a particular observation or set of observations.
-
E.
observedEvent
Indicates that an entity has perceived, detected, or recorded the occurrence of a particular event.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac73be64819083e4a1c2c09551fb |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:09 p.m.