Triple
T29742460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ayn Shams |
E752647
|
entity |
| Predicate | opponentTypeSide1 |
P116577
|
FINISHED |
| Object | Arab tribal forces |
—
|
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: Arab tribal forces | Statement: [Battle of Ayn Shams, opponentTypeSide1, Arab tribal forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentTypeSide1 Context triple: [Battle of Ayn Shams, opponentTypeSide1, Arab tribal forces]
-
A.
opponentCommanderSide
Indicates that one commander is positioned on the opposing side relative to another commander in a conflict or competitive scenario.
-
B.
opponentInCase
Indicates that two parties are on opposing sides in the same legal case or proceeding.
-
C.
opponentGroup
chosen
Indicates that one group is in opposition or conflict with another group, typically as a rival, competitor, or adversary.
-
D.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
E.
firstGameOpponent
Indicates that one entity is the opponent faced by another entity in its first game or match.
- 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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 7:48 p.m.