Triple
T23010349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aduatuci |
E572887
|
entity |
| Predicate | foughtBattleAgainst |
P11113
|
FINISHED |
| Object | Julius Caesar in 57 BC |
—
|
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: Julius Caesar in 57 BC | Statement: [Aduatuci, foughtBattleAgainst, Julius Caesar in 57 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foughtBattleAgainst Context triple: [Aduatuci, foughtBattleAgainst, Julius Caesar in 57 BC]
-
A.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
-
B.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
-
C.
battleAlsoKnownAs
Indicates that a particular battle is known by an alternative name or names.
-
D.
battleOccurred
chosen
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
E.
isPartOfSeriesOfBattlesAt
Indicates that a specific battle belongs to or is included within a larger series of battles occurring at a particular location or during a particular campaign.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18359f5548190b15a139eb09e30a0 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.