Triple
T15474889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gutenberg–Richter law |
E376757
|
entity |
| Predicate | mayDeviateFor |
P53790
|
FINISHED |
| Object | very small earthquakes |
—
|
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: very small earthquakes | Statement: [Gutenberg–Richter law, mayDeviateFor, very small earthquakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayDeviateFor Context triple: [Gutenberg–Richter law, mayDeviateFor, very small earthquakes]
-
A.
mayDifferFrom
chosen
Indicates that one entity is allowed or expected to be different from another entity, without requiring them to be identical.
-
B.
mayAdapt
Indicates that one entity is permitted or allowed to modify, adjust, or alter another entity.
-
C.
mayDelay
Indicates that one entity has the potential or permission to cause a postponement or slowing of another entity, event, or process.
-
D.
mayPass
Indicates that one entity is permitted or authorized to move through, cross, or gain access to another entity or location.
-
E.
mayNot
Indicates that an entity is not permitted or is prohibited from performing a particular action or entering into a specified relationship.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f6e859481909c3d08343b7ad27c |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:34 a.m.