Triple
T17699098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Cannae (1018) |
E441247
|
entity |
| Predicate | regionControlledAfterBattle |
P82949
|
FINISHED |
| Object | parts of Apulia under Byzantine authority |
—
|
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: parts of Apulia under Byzantine authority | Statement: [Battle of Cannae (1018), regionControlledAfterBattle, parts of Apulia under Byzantine authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionControlledAfterBattle Context triple: [Battle of Cannae (1018), regionControlledAfterBattle, parts of Apulia under Byzantine authority]
-
A.
townControlled
Indicates that one entity has governing authority or administrative control over a town.
-
B.
regionInGame
Indicates that a specific region or area exists within or is part of a particular game.
-
C.
controlsRegion
chosen
Indicates that one entity has authoritative power or governing influence over a specified geographic or administrative region.
-
D.
raidedRegion
Indicates that an agent carried out a raid targeting or occurring within a specified region.
-
E.
regionRuled
Indicates that a particular region is governed or controlled by a specified ruler or authority.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47158be9c8190bbf4e5162ff74ad2 |
completed | April 19, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:04 a.m.