Triple
T23681017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eyre Fjord |
E585017
|
entity |
| Predicate | processesObserved |
P34153
|
FINISHED |
| Object | glacier calving |
—
|
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: glacier calving | Statement: [Eyre Fjord, processesObserved, glacier calving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processesObserved Context triple: [Eyre Fjord, processesObserved, glacier calving]
-
A.
observedVia
Indicates that something is perceived, detected, or measured through a particular medium, instrument, method, or channel.
-
B.
observedFor
Indicates that one entity is monitored, watched, or examined over a period of time for the benefit or analysis of another entity.
-
C.
isObservedIn
chosen
Indicates that something (such as a phenomenon, property, or behavior) is detected, recorded, or found to occur within a particular context, setting, or environment.
-
D.
observedEvent
Indicates that an entity has perceived, detected, or recorded the occurrence of a particular event.
-
E.
hasObservation
Indicates that an entity records, contains, or is associated with a specific observation or measured instance.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f835ec8190a7bdcfa48ad79cd5 |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:51 p.m.