Triple
T24294455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sword of Allah |
E605919
|
entity |
| Predicate | notableBattleAssociations |
P23441
|
FINISHED |
| Object | Battle of Uhud |
—
|
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: Battle of Uhud | Statement: [Sword of Allah, notableBattleAssociations, Battle of Uhud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBattleAssociations Context triple: [Sword of Allah, notableBattleAssociations, Battle of Uhud]
-
A.
associatedWithBattle
chosen
Indicates a relationship where an entity is connected or linked to a specific battle, such as by participation, relevance, or involvement.
-
B.
notableBattleRecognized
Indicates that a particular battle is formally acknowledged or recognized as notable in relation to the subject.
-
C.
battlesWith
Indicates that two entities are engaged in active conflict, combat, or struggle against each other.
-
D.
refersToPersonNotableBattle
Indicates that a person is associated with or identified by a specific notable battle in which they played a significant role.
-
E.
notableBattleRole
Indicates the specific role or function an entity played in a notable or historically significant battle.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f291593c0881908a6827f0d8899fe6 |
completed | April 29, 2026, 11:16 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 12:09 a.m.