Triple
T33261044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto Sverdrup expedition |
E851512
|
entity |
| Predicate | shipFrozenInIce |
P14990
|
FINISHED |
| Object | Fram |
—
|
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: Fram | Statement: [Otto Sverdrup expedition, shipFrozenInIce, Fram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipFrozenInIce Context triple: [Otto Sverdrup expedition, shipFrozenInIce, Fram]
-
A.
shipTrappedInIceDate
Indicates the date on which a ship became immobilized or trapped in ice.
-
B.
hasIcebergs
Indicates that one entity (typically a body of water or region) contains or is characterized by the presence of icebergs.
-
C.
frozenIn
chosen
Indicates that one entity is immobilized or preserved in a solid, frozen state within or by another entity.
-
D.
receivesIcebergsFrom
Indicates that one entity is the source or destination in a process where it obtains or is supplied with icebergs from another entity.
-
E.
requiresGlacierTravel
Indicates that performing the activity or reaching the objective necessitates traveling over glacier terrain, typically involving glacier-specific skills and equipment.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:31 a.m.