Triple
T20094991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indigirka River |
E496375
|
entity |
| Predicate | icebound |
P47165
|
FINISHED |
| Object | most of the year |
—
|
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: most of the year | Statement: [Indigirka River, icebound, most of the year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: icebound Context triple: [Indigirka River, icebound, most of the year]
-
A.
iceClass
Indicates a classification relationship specifying the level or category of ice-strengthening or ice-navigation capability assigned to a vessel or structure.
-
B.
frozenIn
Indicates that one entity is immobilized or preserved in a solid, frozen state within or by another entity.
-
C.
iceStrengthened
Indicates that an entity has been made stronger, reinforced, or enhanced through the application or influence of ice.
-
D.
iceFeature
chosen
Indicates a relationship where a geographic or environmental feature is composed of, covered by, or characterized by ice.
-
E.
hasIcebergs
Indicates that one entity (typically a body of water or region) contains or is characterized by the presence of icebergs.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6666b891c8190b4e4a60b73728771 |
completed | April 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:24 p.m.