Triple
T26897105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Freeze |
E677924
|
entity |
| Predicate | effectOnSea |
P41495
|
FINISHED |
| Object | freezes the fjord around Arendelle |
—
|
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: freezes the fjord around Arendelle | Statement: [Great Freeze, effectOnSea, freezes the fjord around Arendelle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnSea Context triple: [Great Freeze, effectOnSea, freezes the fjord around Arendelle]
-
A.
oceanInfluence
chosen
Indicates how the presence, properties, or behavior of an ocean affects another entity, condition, or process.
-
B.
effectOnShips
Indicates the impact or influence that one entity, event, or condition has on ships.
-
C.
seaOf
Indicates a relationship where one entity is metaphorically or literally surrounded or filled by another like a vast sea, emphasizing overwhelming abundance or expansiveness.
-
D.
endSea
Indicates that something marks the boundary or termination point of a sea or sea area.
-
E.
landfallEffect
Indicates the impact or consequences that occur when a storm or similar weather system moves from water onto land.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 5:48 a.m.