Triple
T16178344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hussein Kamel of Egypt |
E392622
|
entity |
| Predicate | installedAsMonarchBy |
P122009
|
FINISHED |
| Object | British authorities in 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 authorities in Egypt | Statement: [Hussein Kamel of Egypt, installedAsMonarchBy, British authorities in Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: installedAsMonarchBy Context triple: [Hussein Kamel of Egypt, installedAsMonarchBy, British authorities in Egypt]
-
A.
installedAsKingAfter
Indicates that one entity was formally placed into the position of king following the reign or rule of another entity.
-
B.
appliedToMonarch
Indicates that an action, policy, or attribute is directed toward or exercised upon a monarch.
-
C.
monarchUntil
Indicates that an entity served as monarch over another entity up to, but not beyond, a specified end time or event.
-
D.
monarchIn
Indicates that a person serves as the ruling monarch of a specified country, state, or territory.
-
E.
includesMonarch
Indicates that one entity contains, comprises, or has as part of it a particular monarch as a member or constituent.
- F. None of above. chosen
Provenance (4 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205ab3108190a84fc2dfe61d5044 |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:02 a.m.