Triple
T18138280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lago Fagnano |
E434192
|
entity |
| Predicate | hasIceRelatedFeature |
P79436
|
FINISHED |
| Object | glacially carved basin |
—
|
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: glacially carved basin | Statement: [Lago Fagnano, hasIceRelatedFeature, glacially carved basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIceRelatedFeature Context triple: [Lago Fagnano, hasIceRelatedFeature, glacially carved basin]
-
A.
hasIceFeature
chosen
Indicates that one entity possesses, contains, or is characterized by an ice-related feature or formation.
-
B.
hasIceType
Indicates that an entity possesses or is associated with the Ice elemental type or attribute.
-
C.
hasIceClass
Indicates that an object (typically a vessel or structure) is assigned a specific ice classification denoting its capability to operate in icy or ice-infested waters.
-
D.
hasIceShelf
Indicates that a glacier, ice sheet, or coastline possesses an attached floating extension of ice known as an ice shelf.
-
E.
hasIceSurface
Indicates that an entity possesses or is characterized by a surface composed primarily of ice.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de089f1881908dff9835be5129a1 |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.