Triple
T5722497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish Thermopylae |
E126178
|
entity |
| Predicate | hasMainCombatant |
P3861
|
FINISHED |
| Object | Polish defenders |
—
|
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: Polish defenders | Statement: [Polish Thermopylae, hasMainCombatant, Polish defenders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainCombatant Context triple: [Polish Thermopylae, hasMainCombatant, Polish defenders]
-
A.
mainCombatant
chosen
Indicates that the subject is the primary participant or leading party in a conflict, battle, or combat situation involving the object.
-
B.
hasCombatantSide
Indicates a relationship where a conflict, battle, or war is associated with one of the participating sides or factions involved in the combat.
-
C.
combatantsIncluded
Indicates that the specified entities are participants or parties involved in a particular combat or conflict.
-
D.
hasOpposingFront
Indicates that one entity’s front side is directly facing or oriented opposite to the front side of another entity.
-
E.
mainAttacker
Indicates that an entity is the primary or leading aggressor responsible for initiating or carrying out an attack against another entity.
- 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_69c0082f723881908ce8bb13a0c0f8b7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c47f4c81909e6849c3be3e951c |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:46 p.m.