Triple
T7863067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loubet Coast |
E182546
|
entity |
| Predicate | hasIceFeature |
P79436
|
FINISHED |
| Object | tidewater glaciers |
—
|
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: tidewater glaciers | Statement: [Loubet Coast, hasIceFeature, tidewater glaciers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIceFeature Context triple: [Loubet Coast, hasIceFeature, tidewater glaciers]
-
A.
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.
-
B.
hasIceType
Indicates that an entity possesses or is associated with the Ice elemental type or attribute.
-
C.
hasIceShelf
Indicates that a glacier, ice sheet, or coastline possesses an attached floating extension of ice known as an ice shelf.
-
D.
hasIceFront
Indicates that an entity possesses or is characterized by an ice-covered front or leading edge.
-
E.
hasIceSource
Indicates that one entity serves as the origin or provider of ice for another entity.
- F. None of above. chosen
Provenance (4 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_69ca82887fd48190975896bf38c4596b |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb36bfd8a4819093c2ef6d47891a68 |
completed | March 31, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf786ec748190b6347b0c94335550 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:54 p.m.