Triple
T1755770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Charlotte Fault |
E38542
|
entity |
| Predicate | slipRate |
P7349
|
FINISHED |
| Object | high relative plate motion rate |
—
|
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: high relative plate motion rate | Statement: [Queen Charlotte Fault, slipRate, high relative plate motion rate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: slipRate Context triple: [Queen Charlotte Fault, slipRate, high relative plate motion rate]
-
A.
averageSlipRate
chosen
Indicates the typical rate at which displacement or movement occurs along a fault or interface over a specified period of time.
-
B.
slipType
Indicates the specific category or kind of slip involved in an action or relationship between entities.
-
C.
spinRate
Indicates the rotational speed at which an object or system is spinning, typically measured as revolutions per unit time.
-
D.
spreadingRateType
Indicates the manner or category of how quickly or in what way something spreads or propagates.
-
E.
averageSpreadingRate
Indicates the typical rate at which something (such as a phenomenon, substance, or influence) expands or propagates over a given distance or time.
- 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_69a8862bdb2081908aefe831c8aa8017 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aba6a63f588190b53b39c6b97d74f4 |
completed | March 7, 2026, 4:16 a.m. |
| PD | Predicate disambiguation | batch_69aa61c7ef4c8190abec87c96a787d82 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.