Triple
T31993146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lankaran |
E816921
|
entity |
| Predicate | combatantCommander (Qajar Iran) |
P46041
|
FINISHED |
| Object | Sadiq Khan |
—
|
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: Sadiq Khan | Statement: [Battle of Lankaran, combatantCommander (Qajar Iran), Sadiq Khan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantCommander (Qajar Iran) Context triple: [Battle of Lankaran, combatantCommander (Qajar Iran), Sadiq Khan]
-
A.
AfghanCommander
Indicates that an entity serves in the role of a military commander associated with Afghanistan.
-
B.
PersianCommander
chosen
Indicates that an entity serves as a military commander for, or in the context of, the Persian forces or Persian polity.
-
C.
combatant2Commander
Indicates that a combatant serves under the authority or command of a specific commander.
-
D.
IraqiCommander
Indicates a relationship where an individual serves in the role of a military commander for Iraqi armed or security forces.
-
E.
commanderForGhaznavids
Indicates that a person served as a military commander on behalf of the Ghaznavid state or dynasty.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 12:13 a.m.