Triple
T32965802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gowganda Formation |
E843362
|
entity |
| Predicate | hasTypeOfGlacialDeposit |
P198468
|
FINISHED |
| Object | tillite |
—
|
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: tillite | Statement: [Gowganda Formation, hasTypeOfGlacialDeposit, tillite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfGlacialDeposit Context triple: [Gowganda Formation, hasTypeOfGlacialDeposit, tillite]
-
A.
hasGlacialLandforms
Indicates that an entity possesses or contains landforms that were created or shaped by glacial activity.
-
B.
hasGlacialProcess
Indicates a relationship where something is shaped, formed, or affected by the actions or dynamics of glaciers or glacial activity.
-
C.
hasGlacialEnvironment
Indicates that an entity exists in, is associated with, or is characterized by a glacial or glacier-influenced environment.
-
D.
isGlacialLake
Indicates that a body of water is classified as a glacial lake, formed by the action or presence of glaciers.
-
E.
glacierType
Indicates the specific classification or category of a glacier based on its form, dynamics, or setting.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fee691952c8190822da83e46311d1d |
completed | May 9, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69fee62f285c8190a625562a9b80526e |
completed | May 9, 2026, 7:45 a.m. |
| PDg | Predicate description generation | batch_69fee690af688190a845310f102a0c83 |
completed | May 9, 2026, 7:47 a.m. |
Created at: May 1, 2026, 1:21 a.m.