Triple
T30331983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Adrianople |
E771504
|
entity |
| Predicate | combatantTypeGothic |
P88504
|
FINISHED |
| Object | federated and refugee Gothic groups |
—
|
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: federated and refugee Gothic groups | Statement: [Battle of Adrianople, combatantTypeGothic, federated and refugee Gothic groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantTypeGothic Context triple: [Battle of Adrianople, combatantTypeGothic, federated and refugee Gothic groups]
-
A.
isCombatUnit
Indicates that an entity functions as a unit specifically designated and equipped to engage in combat operations.
-
B.
combatantsNationality
Indicates that the entities involved in a combat or conflict share or are associated with a specified nationality.
-
C.
combatantsIncluded
Indicates that the specified entities are participants or parties involved in a particular combat or conflict.
-
D.
combatantTribe
chosen
Indicates a tribal group that participates as a fighter or belligerent party in a conflict or battle.
-
E.
eraOfWarfare
Indicates a historical period characterized by significant or sustained warfare.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 7:53 p.m.