Triple
T13747257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teton fault |
E330244
|
entity |
| Predicate | hasSlipRate |
P7349
|
FINISHED |
| Object | approximately 1 to 2 millimeters per year |
—
|
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: approximately 1 to 2 millimeters per year | Statement: [Teton fault, hasSlipRate, approximately 1 to 2 millimeters per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSlipRate Context triple: [Teton fault, hasSlipRate, approximately 1 to 2 millimeters per year]
-
A.
slipType
Indicates the specific category or kind of slip involved in an action or relationship between entities.
-
B.
averageSlipRate
chosen
Indicates the typical rate at which displacement or movement occurs along a fault or interface over a specified period of time.
-
C.
hasRateType
Indicates the specific category or scheme under which a rate (such as a price, fee, or interest) is defined or applied.
-
D.
maximumSlip
Indicates the greatest allowable or observed amount of slip between two contacting or interacting elements in a system.
-
E.
hasSlopeProtection
Indicates that a slope or embankment is equipped with protective measures or structures to prevent erosion, instability, or damage.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02132a108190aca728b95e83af01 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:08 p.m.