Triple
T29115702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Nedao |
E737038
|
entity |
| Predicate | combatantsStatusAfter |
P109227
|
FINISHED |
| Object | Independent Germanic and other tribal kingdoms |
—
|
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: Independent Germanic and other tribal kingdoms | Statement: [Battle of the Nedao, combatantsStatusAfter, Independent Germanic and other tribal kingdoms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantsStatusAfter Context triple: [Battle of the Nedao, combatantsStatusAfter, Independent Germanic and other tribal kingdoms]
-
A.
combatantsStatusBefore
Indicates the condition or status of the involved combatants immediately prior to a combat or conflict event.
-
B.
statusAfterAttack
Indicates the resulting condition or state of an entity after an attack has occurred.
-
C.
statusAfterBattle
chosen
Indicates the condition or state of an entity following the completion of a battle or combat encounter.
-
D.
combatantsIncluded
Indicates that the specified entities are participants or parties involved in a particular combat or conflict.
-
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.
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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 11:22 a.m.