Triple
T35959420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Storm of 1913 |
E1039954
|
entity |
| Predicate | affectedActivity |
P48591
|
FINISHED |
| Object | Great Lakes shipping |
—
|
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: Great Lakes shipping | Statement: [Great Storm of 1913, affectedActivity, Great Lakes shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedActivity Context triple: [Great Storm of 1913, affectedActivity, Great Lakes shipping]
-
A.
associatedActivity
chosen
Indicates that one entity is linked to, involved in, or characterized by a particular activity or set of activities.
-
B.
affectedSubject
Indicates that an entity is the one that experiences or is impacted by an action, event, or condition.
-
C.
affectedEntity
Indicates that an entity is the one that is impacted, influenced, or acted upon as a result of an event, action, or process.
-
D.
relativeActivity
Indicates a comparison of the level, intensity, or amount of an activity between entities or conditions.
-
E.
affectedClass
Indicates that one entity (typically a change, event, or issue) has an impact on or is relevant to a particular class or category of items.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:07 p.m.