Triple
T18550063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Sisak |
E453348
|
entity |
| Predicate | strengthOttoman |
P131194
|
FINISHED |
| Object | approximately 8,000–12,000 soldiers |
—
|
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: approximately 8,000–12,000 soldiers | Statement: [Battle of Sisak, strengthOttoman, approximately 8,000–12,000 soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthOttoman Context triple: [Battle of Sisak, strengthOttoman, approximately 8,000–12,000 soldiers]
-
A.
OttomanStrength
chosen
Indicates the level or degree of military, political, or economic power possessed or exerted by the Ottoman Empire in a given context.
-
B.
strengthRussoAustrian
Indicates the relative military or political strength between Russian and Austrian forces or interests in a given context.
-
C.
primaryTacticOttomans
Indicates the main military or strategic method predominantly employed by the Ottoman forces in a given conflict or context.
-
D.
OttomanRole
Indicates that an entity holds or held a specific role, position, or function within the Ottoman Empire.
-
E.
outcomeForOttomans
Indicates the result or consequence experienced by the Ottoman side in a given event, action, or situation.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534beeb408190a03f6d7c3f2ef389 |
completed | April 19, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:38 a.m.