Triple
T23212590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Heliopolis (1800) |
E580638
|
entity |
| Predicate | opposingForceComposition |
P55225
|
FINISHED |
| Object | Ottoman infantry, cavalry, and artillery |
—
|
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: Ottoman infantry, cavalry, and artillery | Statement: [Battle of Heliopolis (1800), opposingForceComposition, Ottoman infantry, cavalry, and artillery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposingForceComposition Context triple: [Battle of Heliopolis (1800), opposingForceComposition, Ottoman infantry, cavalry, and artillery]
-
A.
opposingForce
Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of another entity.
-
B.
redForcesComposition
chosen
Indicates the makeup or structure of the red (opposing) forces in terms of their constituent units, capabilities, or elements.
-
C.
opposingAlliance
Indicates that two entities belong to rival or mutually opposed alliances or factions.
-
D.
forcesComposition
Indicates that one entity compels or determines the structural makeup or arrangement of another entity.
-
E.
opposingUnits
Indicates that two units are in opposition to each other, such as being on rival sides, conflicting forces, or competing entities within a given context.
- 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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f191620378819096362252c3b819b6 |
completed | April 29, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:07 p.m.