Triple
T28757974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muʾtah |
E731723
|
entity |
| Predicate | battleOutcomeCharacterization |
P15636
|
FINISHED |
| Object | tactically inconclusive |
—
|
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: tactically inconclusive | Statement: [Muʾtah, battleOutcomeCharacterization, tactically inconclusive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleOutcomeCharacterization Context triple: [Muʾtah, battleOutcomeCharacterization, tactically inconclusive]
-
A.
resultOfBattle
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
B.
battleOutcomeRole
Indicates the specific role an entity played in a battle with respect to its outcome (e.g., victor, loser, ally, defender).
-
C.
tacticalOutcome
chosen
Indicates the specific result or consequence produced by a particular tactic or tactical action in a given situation.
-
D.
battleDescribed
Indicates that a particular battle is described, depicted, or recounted in the referenced source or representation.
-
E.
resultOfMilitaryCampaign
Indicates that one event, condition, or outcome occurs as a direct consequence of a specified military campaign.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 6:10 a.m.