Triple
T2894740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garlock Fault |
E63908
|
entity |
| Predicate | slipSense |
P27394
|
FINISHED |
| Object | sinistral |
—
|
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: sinistral | Statement: [Garlock Fault, slipSense, sinistral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: slipSense Context triple: [Garlock Fault, slipSense, sinistral]
-
A.
slipType
Indicates the specific category or kind of slip involved in an action or relationship between entities.
-
B.
dominantSlipSense
chosen
Indicates the primary direction or mode in which slip or displacement occurs along a fault or between two surfaces.
-
C.
maximumSlip
Indicates the greatest allowable or observed amount of slip between two contacting or interacting elements in a system.
-
D.
gripType
Indicates the manner or style in which one entity physically holds or grasps another.
-
E.
averageSlipRate
Indicates the typical rate at which displacement or movement occurs along a fault or interface over a specified period of 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe063de6c8190bce9ddefd1dd62e1 |
completed | March 7, 2026, 8:23 a.m. |
| PD | Predicate disambiguation | batch_69abdd17bcdc8190aa47274a50ba4ad4 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:07 p.m.