Triple
T18320881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LeConte Glacier |
E438874
|
entity |
| Predicate | calvingInto |
P50125
|
FINISHED |
| Object | saltwater |
—
|
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: saltwater | Statement: [LeConte Glacier, calvingInto, saltwater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calvingInto Context triple: [LeConte Glacier, calvingInto, saltwater]
-
A.
calvingProcess
Indicates the process in which a cow gives birth to a calf, encompassing the stages and actions involved in parturition.
-
B.
calvingProduces
Indicates that the biological process of calving results in or brings about a particular outcome, product, or entity.
-
C.
calvingGrounds
Indicates areas where animals, typically large mammals, go to give birth and rear their newborns.
-
D.
hasCalvingActivity
Indicates that an entity exhibits or is associated with calving behavior or events, such as giving birth or breaking off in distinct portions.
-
E.
hasMeltwaterContributionTo
chosen
Indicates that one entity contributes meltwater (from melting ice or snow) to another entity, such as a water body or hydrological system.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aa5a3508190a3025e71c11d79e2 |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.