Triple
T32505931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claudius II Gothicus |
E830791
|
entity |
| Predicate | militaryCampaignRegion |
P40156
|
FINISHED |
| Object | Balkans |
—
|
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: Balkans | Statement: [Claudius II Gothicus, militaryCampaignRegion, Balkans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryCampaignRegion Context triple: [Claudius II Gothicus, militaryCampaignRegion, Balkans]
-
A.
militaryCampaignOf
Indicates a relationship where a specific military campaign is conducted by, initiated by, or belongs to a particular military force, state, or commander.
-
B.
militaryCampaignsIn
chosen
Indicates that a military campaign took place within, or was conducted in, a specified geographic or political area.
-
C.
regionOfConflict
Indicates that a specified region is the location where a particular conflict or dispute takes place.
-
D.
militaryCampaigns
Indicates that an entity conducts, participates in, or is associated with organized military operations or campaigns against another entity or within a specific conflict.
-
E.
battlefieldOf
Indicates that a location is the site where a particular battle or military engagement took place.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 1, 2026, 1 a.m.