Triple
T23464536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saad Zaghloul |
E569068
|
entity |
| Predicate | causeOfNotableEvent |
P100753
|
FINISHED |
| Object | British protectorate over Egypt |
—
|
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: British protectorate over Egypt | Statement: [Saad Zaghloul, causeOfNotableEvent, British protectorate over Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfNotableEvent Context triple: [Saad Zaghloul, causeOfNotableEvent, British protectorate over Egypt]
-
A.
causeCélèbre
Indicates a relationship where an event, issue, or person becomes widely known and intensely debated or celebrated in public discourse.
-
B.
hasNamesakeNotableEvent
Indicates that one entity serves as the namesake for a notable event associated with the other entity.
-
C.
possibleCauseOfNotability
chosen
Indicates that one entity is a potential reason or contributing factor for why another entity is notable or recognized.
-
D.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
-
E.
famousForEvent
Indicates that an entity is widely known or recognized specifically because of a particular 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a6f9e59081909e8cf224ee46109c |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:54 p.m.