Triple
T18287542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Gravia Inn |
E438021
|
entity |
| Predicate | OttomanStrength |
P131194
|
FINISHED |
| Object | several thousand men |
—
|
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: several thousand men | Statement: [Battle of Gravia Inn, OttomanStrength, several thousand men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OttomanStrength Context triple: [Battle of Gravia Inn, OttomanStrength, several thousand men]
-
A.
OttomanRole
Indicates that an entity holds or held a specific role, position, or function within the Ottoman Empire.
-
B.
OttomanCommander
Indicates that an entity serves in the role of a military commander within the Ottoman Empire.
-
C.
primaryTacticOttomans
Indicates the main military or strategic method predominantly employed by the Ottoman forces in a given conflict or context.
-
D.
outcomeForOttomans
Indicates the result or consequence experienced by the Ottoman side in a given event, action, or situation.
-
E.
strategicObjectiveOttoman
Indicates that one entity serves as or relates to a strategic objective or goal specifically concerning the Ottoman Empire.
- F. None of above. chosen
Provenance (4 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e500faf62081908f16ebee0a195ba2 |
completed | April 19, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:35 a.m.