Triple
T34933340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1992 Landers earthquake |
E1007500
|
entity |
| Predicate | slipMaximum |
P34011
|
FINISHED |
| Object | about 6 meters |
—
|
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: about 6 meters | Statement: [1992 Landers earthquake, slipMaximum, about 6 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: slipMaximum Context triple: [1992 Landers earthquake, slipMaximum, about 6 meters]
-
A.
maximumSlip
chosen
Indicates the greatest allowable or observed amount of slip between two contacting or interacting elements in a system.
-
B.
slipType
Indicates the specific category or kind of slip involved in an action or relationship between entities.
-
C.
setsMaximum
Indicates that one entity establishes an upper limit or maximum allowable value for another entity or quantity.
-
D.
maximumSlotsRecommended
Indicates the highest number of slots that is advised or suggested to be used in a given context.
-
E.
definesMaximum
Indicates that one entity specifies or sets the upper limit or greatest allowable value for another entity.
- 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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.