Triple
T35676361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish Vega Expedition |
E1030870
|
entity |
| Predicate | navigatedThrough |
P36970
|
FINISHED |
| Object | Kara Sea |
—
|
NE NERFINISHED |
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: Kara Sea | Statement: [Swedish Vega Expedition, navigatedThrough, Kara Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigatedThrough Context triple: [Swedish Vega Expedition, navigatedThrough, Kara Sea]
-
A.
navigatedIn
chosen
Indicates that an entity moved or steered through or within a particular medium, environment, or space.
-
B.
navigatedFor
Indicates that one entity moved or directed a path specifically on behalf of, or in service to, another entity.
-
C.
navigatedAround
Indicates that one entity moved in such a way as to go past or circumvent another entity or obstacle without directly passing through or over it.
-
D.
navigatedSince
Indicates that one entity has been navigating or has maintained a navigation state continuously from a specified point in time onward.
-
E.
navigatedBy
Indicates that the movement, direction, or operation of something is controlled, guided, or steered by a specified agent.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.