Triple
T70740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1989 Loma Prieta earthquake |
E1415
|
entity |
| Predicate | occurredDuring |
P3824
|
FINISHED |
| Object | Game 3 of the 1989 World Series |
—
|
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: Game 3 of the 1989 World Series | Statement: [1989 Loma Prieta earthquake, occurredDuring, Game 3 of the 1989 World Series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occurredDuring Context triple: [1989 Loma Prieta earthquake, occurredDuring, Game 3 of the 1989 World Series]
-
A.
enactedDuring
Indicates that an action, event, or state occurred within the temporal span of a specified time period or event.
-
B.
operatedDuring
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
-
C.
writtenDuring
Indicates that the creation or authorship of something took place within a specified time period or historical event.
-
D.
awardedDuring
Indicates that an award or honor was given to an entity within a specified time period or event.
-
E.
meetsDuring
Indicates that one entity encounters or comes together with another while a specified event or time interval is in progress.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24eaa0df88190add55579b2b9fd02 |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a24fcf5a88819088c5fa4c08476358 |
completed | Feb. 28, 2026, 2:15 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.