Triple
T394183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suez Canal |
E8943
|
entity |
| Predicate | blockageDate |
P6878
|
FINISHED |
| Object | 2021-03-23 |
—
|
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: 2021-03-23 | Statement: [Suez Canal, blockageDate, 2021-03-23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockageDate Context triple: [Suez Canal, blockageDate, 2021-03-23]
-
A.
immediateCauseDate
Indicates the specific date on which an event or condition directly caused another event or outcome to occur.
-
B.
dateOfSubmission
Indicates the specific date on which something (such as a document, application, or assignment) was formally submitted.
-
C.
ordinationDate
Indicates the date on which an individual was formally ordained to a religious office or role.
-
D.
dateOf
chosen
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
E.
surrenderDate
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec77a8a08190b6f96373aa8c1346 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96bd3848190a66ca14dfbd26da5 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.