Triple
T14038076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nuclear icebreaker Arktika |
E337764
|
entity |
| Predicate | reachedNorthPole |
P84015
|
FINISHED |
| Object | 1977-08-17 |
—
|
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: 1977-08-17 | Statement: [nuclear icebreaker Arktika, reachedNorthPole, 1977-08-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachedNorthPole Context triple: [nuclear icebreaker Arktika, reachedNorthPole, 1977-08-17]
-
A.
reachedSouthPoleDate
Indicates the date on which an entity arrived at or reached the South Pole.
-
B.
claimedArrivalDateAtPole
chosen
Indicates the date on which an entity asserts or reports having arrived at a geographic pole.
-
C.
reachedSummitWith
Indicates that one entity arrived at or attained the summit together with another entity, as part of the same ascent or achievement.
-
D.
locatedAtPoleRegion
Indicates that an entity is situated within a polar region of a planetary body, such as its north or south pole area.
-
E.
reachesSummit
Indicates that an entity successfully arrives at or attains the highest point or summit of something.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de30ee374081908b6b5e8f81dd90f2 |
completed | April 14, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.