Triple
T70472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haymarket affair |
E1409
|
entity |
| Predicate | hasTriggerEvent |
P693
|
FINISHED |
| Object | McCormick Harvesting Machine Company strike |
—
|
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: McCormick Harvesting Machine Company strike | Statement: [Haymarket affair, hasTriggerEvent, McCormick Harvesting Machine Company strike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTriggerEvent Context triple: [Haymarket affair, hasTriggerEvent, McCormick Harvesting Machine Company strike]
-
A.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
-
B.
triggered
chosen
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
C.
hasKeyEvent
Indicates that an entity includes, is associated with, or is characterized by a significant or defining event.
-
D.
hasCause
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
-
E.
basedOnEvent
Indicates that something is derived from, influenced by, or determined in reference to a specific event.
- 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_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. |
Created at: Feb. 28, 2026, 2:03 a.m.