Triple
T24812556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptian campaign into Najd |
E620826
|
entity |
| Predicate | executedLeader |
P157370
|
FINISHED |
| Object | Abdullah bin Saud |
—
|
NE NERFINISHED |
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: Abdullah bin Saud | Statement: [Egyptian campaign into Najd, executedLeader, Abdullah bin Saud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executedLeader Context triple: [Egyptian campaign into Najd, executedLeader, Abdullah bin Saud]
-
A.
capturedLeader
Indicates that one party has taken control of and detained the primary leader of another group or entity.
-
B.
carriedLeader
Indicates that one entity physically transported or bore a leader from one place or situation to another.
-
C.
servedUnderLeader
Indicates that one entity held a position or role subordinate to, and operating under the authority or command of, another specified leader.
-
D.
laterLeader
Indicates that one entity serves as a leader or holds a leadership role at a later time than another specified leader.
-
E.
establishedUnderLeader
Indicates that an entity was founded, created, or formally established during the tenure or authority of a specific leader.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f42b11251881908070b93355de64ad |
completed | May 1, 2026, 4:24 a.m. |
Created at: April 18, 2026, 4:51 a.m.