Triple
T24812557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptian campaign into Najd |
E620826
|
entity |
| Predicate | executedLeaderExecutionPlace |
P157741
|
FINISHED |
| Object | Istanbul |
—
|
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: Istanbul | Statement: [Egyptian campaign into Najd, executedLeaderExecutionPlace, Istanbul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executedLeaderExecutionPlace Context triple: [Egyptian campaign into Najd, executedLeaderExecutionPlace, Istanbul]
-
A.
executedLeader
Indicates that a leader was put to death, typically as a result of a formal or authoritative execution.
-
B.
capturedLeader
Indicates that one party has taken control of and detained the primary leader of another group or entity.
-
C.
executionDateOfLeader
Indicates the date on which a leader was executed.
-
D.
servedUnderLeader
Indicates that one entity held a position or role subordinate to, and operating under the authority or command of, another specified leader.
-
E.
capturedByLeader
Indicates that an entity has been taken or seized under the control or authority of a 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_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f44a3adb7c8190941572f718b3b93c |
completed | May 1, 2026, 6:37 a.m. |
Created at: April 18, 2026, 4:51 a.m.