Triple
T3250344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1992 Cape Mendocino earthquakes |
E68161
|
entity |
| Predicate | mainshockTimeUTC |
P46840
|
FINISHED |
| Object | 1992-04-25T18:06:00Z |
—
|
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: 1992-04-25T18:06:00Z | Statement: [1992 Cape Mendocino earthquakes, mainshockTimeUTC, 1992-04-25T18:06:00Z]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainshockTimeUTC Context triple: [1992 Cape Mendocino earthquakes, mainshockTimeUTC, 1992-04-25T18:06:00Z]
-
A.
timeOfMainAssault
Indicates the specific time at which the primary or main assault event occurred.
-
B.
impactTimeEasternDaylightTime
Indicates the specific time at which an impact occurs, expressed in Eastern Daylight Time.
-
C.
timeOfInitiation
Indicates the specific point in time at which an action, event, or process begins.
-
D.
impactTimeLocal
Indicates the specific local time at which an impact event occurs or is expected to occur.
-
E.
hijackingTimeApproximate
Indicates that the time at which a hijacking occurred is known only approximately rather than as an exact timestamp.
- F. None of above. chosen
Provenance (4 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_69ad858e4c708190aa31d486cfee8a6a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf40f7908190a450c3136fccb020 |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada41837e48190933572165be0ca38 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada525bb2c8190b773efe6d696b6ab |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:09 p.m.