Triple
T5554727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viedma Glacier |
E145609
|
entity |
| Predicate | hasFrontType |
P697
|
FINISHED |
| Object | tidewater-like lake-terminating front |
—
|
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-like lake-terminating front | Statement: [Viedma Glacier, hasFrontType, tidewater-like lake-terminating front]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFrontType Context triple: [Viedma Glacier, hasFrontType, tidewater-like lake-terminating front]
-
A.
hasFront
Indicates that an entity possesses or is associated with a front-facing side, surface, or portion.
-
B.
hasFrontColumns
Indicates that one entity possesses or features columns located at its front side.
-
C.
frontType
chosen
Indicates the type or category of a front (e.g., boundary or leading side) that one entity presents or forms relative to another.
-
D.
hasFrontPerson
Indicates that an entity is represented, led, or fronted publicly by a specific person.
-
E.
hasFrontend
Indicates that one entity serves as the user-facing interface or presentation layer for another entity.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01ffaf4fc8190bf27014d21954a70 |
completed | March 22, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.