Triple
T17699076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Cannae (1018) |
E441247
|
entity |
| Predicate | NormanLeader |
P105968
|
FINISHED |
| Object | Gilbert Buatère |
—
|
NE NERFINISHED |
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: Gilbert Buatère | Statement: [Battle of Cannae (1018), NormanLeader, Gilbert Buatère]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NormanLeader Context triple: [Battle of Cannae (1018), NormanLeader, Gilbert Buatère]
-
A.
GermanicLeader
Indicates that an entity serves as a leader or ruling figure within a Germanic group, tribe, or people.
-
B.
EarlMarshal
Indicates a person holds the office or role of Earl Marshal in relation to a sovereign, state, or ceremonial hierarchy.
-
C.
commanderOfFrankishForces
Indicates that one entity serves as the commander of the Frankish military forces in relation to another entity or context.
-
D.
notableLeaderSide
chosen
Indicates that a person is a prominent or distinguished leader associated with a particular side, faction, or party in a conflict or competition.
-
E.
dateLeaderEnthroned
Indicates the specific date on which a leader formally assumed or was installed into their position of 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.