Triple
T22544920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1999 Düzce earthquake |
E557393
|
entity |
| Predicate | timeBetweenMainEvents |
P148599
|
FINISHED |
| Object | about three months after the İzmit earthquake |
—
|
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 three months after the İzmit earthquake | Statement: [1999 Düzce earthquake, timeBetweenMainEvents, about three months after the İzmit earthquake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeBetweenMainEvents Context triple: [1999 Düzce earthquake, timeBetweenMainEvents, about three months after the İzmit earthquake]
-
A.
timeCoMainEvent
Indicates that two or more events occur as co-main events at the same time or within the same overarching event timeframe.
-
B.
timePeriodEvent
Indicates that an event occurs, is scheduled, or is valid within a specified time period.
-
C.
numberOfMainEvents
Indicates the total count of primary or most significant events associated with a given entity or context.
-
D.
timeIntervalLength
Indicates the duration or length of a specified time interval.
-
E.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69e11e58662081909ae346ab384514ca |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f34a0688190ad55be067db8e21b |
completed | April 29, 2026, 1:30 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:51 p.m.