Triple
T29115701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Nedao |
E737038
|
entity |
| Predicate | combatantsStatusBefore |
P167400
|
FINISHED |
| Object | Subject peoples under Hunnic overlordship |
—
|
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: Subject peoples under Hunnic overlordship | Statement: [Battle of the Nedao, combatantsStatusBefore, Subject peoples under Hunnic overlordship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantsStatusBefore Context triple: [Battle of the Nedao, combatantsStatusBefore, Subject peoples under Hunnic overlordship]
-
A.
fighter2StatusBeforeFight
Indicates the condition or state of the second fighter immediately prior to the fight.
-
B.
fighter1StatusBeforeFight
Indicates the condition or state of the first fighter immediately prior to the start of the fight.
-
C.
combatantsIncluded
Indicates that the specified entities are participants or parties involved in a particular combat or conflict.
-
D.
statusOfCityBeforeBattle
Indicates the condition or situation a city was in immediately prior to a specific battle.
-
E.
opposingForcesStatus
Indicates the current state or condition of two or more forces that are in conflict or opposition to each other.
- F. None of above. chosen
Provenance (4 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 11:22 a.m.