Triple
T10624609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H3RC |
E250289
|
entity |
| Predicate | associatedWithNotableIncident |
P18677
|
FINISHED |
| Object | Grounding in Suez Canal on 23 March 2021 |
—
|
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: Grounding in Suez Canal on 23 March 2021 | Statement: [H3RC, associatedWithNotableIncident, Grounding in Suez Canal on 23 March 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithNotableIncident Context triple: [H3RC, associatedWithNotableIncident, Grounding in Suez Canal on 23 March 2021]
-
A.
notableIncidentType
Indicates the specific category or kind of significant event or incident associated with an entity.
-
B.
notableProtectiveIncident
Indicates that a significant event occurred in which one entity protected or defended another in a notable or remarkable way.
-
C.
hasNotableIncident
chosen
Indicates that an entity is associated with a significant or noteworthy event, occurrence, or incident.
-
D.
significantEventInvolves
Indicates that a significant event includes or engages a particular entity as a participant or key element.
-
E.
closelyAssociatedEvent
Indicates that one event is strongly related to, connected with, or occurs in close conjunction with another 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df7fe9fc81908b3b8d1dc06a829c |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 8:53 p.m.