Triple
T2300024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suez Canal Company |
E51708
|
entity |
| Predicate | concessionPlannedEnd |
P33786
|
FINISHED |
| Object | 1968 |
—
|
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: 1968 | Statement: [Suez Canal Company, concessionPlannedEnd, 1968]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concessionPlannedEnd Context triple: [Suez Canal Company, concessionPlannedEnd, 1968]
-
A.
concessionExpiry
chosen
Indicates that a granted concession or special permission remains valid only until a specified expiration time or date.
-
B.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
C.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
D.
plannedAt
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
-
E.
concludedAt
Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
- 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_69a88b0a9f248190bcff941463d8f65a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcbabf01081908db3b42bc7c60444 |
completed | March 7, 2026, 6:54 a.m. |
| PD | Predicate disambiguation | batch_69abc58ad33c8190b8d68af41b6f5e07 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.