Triple
T24334189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rutford Ice Stream |
E613331
|
entity |
| Predicate | dischargeSpeed |
P155514
|
FINISHED |
| Object | over 1 m per day in places |
—
|
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: over 1 m per day in places | Statement: [Rutford Ice Stream, dischargeSpeed, over 1 m per day in places]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dischargeSpeed Context triple: [Rutford Ice Stream, dischargeSpeed, over 1 m per day in places]
-
A.
flowSpeed
chosen
Indicates the rate at which a fluid or medium moves through a given point or along a path over time.
-
B.
dischargeAverage
Indicates the typical or mean rate at which something (such as fluid, electricity, or emissions) is released or flows over a given period.
-
C.
dropSpeed
Indicates the rate at which an object or entity decreases in height or position over time while falling or being dropped.
-
D.
maximumDischarge
Indicates the greatest allowable or observed rate at which something can be discharged or released from a source.
-
E.
displacementRate
Indicates the rate at which an entity’s position changes over time relative to a reference point or frame.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292f381b08190b529a765a5d5e89b |
completed | April 29, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:56 a.m.