Triple
T3276102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Catalaunian Plains |
E68760
|
entity |
| Predicate | combatantsSide2 |
P375
|
FINISHED |
| Object | Huns and subject peoples |
—
|
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: Huns and subject peoples | Statement: [Battle of the Catalaunian Plains, combatantsSide2, Huns and subject peoples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantsSide2 Context triple: [Battle of the Catalaunian Plains, combatantsSide2, Huns and subject peoples]
-
A.
combatantsIncluded
Indicates that the specified entities are participants or parties involved in a particular combat or conflict.
-
B.
commandersSide
Indicates that one entity is on the same side, faction, or team as the commander in a conflict or competitive context.
-
C.
conflictSide
chosen
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
-
D.
combatantStrength
Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
-
E.
opposingAlliance
Indicates that two entities belong to rival or mutually opposed alliances or factions.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0110f1c8190ae60708b686cbbf9 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.