Triple
T29352508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian fascism |
E744349
|
entity |
| Predicate | alliedMilitaryPower |
P61211
|
FINISHED |
| Object | Axis Powers |
—
|
NE NERFINISHED |
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: Axis Powers | Statement: [Hungarian fascism, alliedMilitaryPower, Axis Powers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alliedMilitaryPower Context triple: [Hungarian fascism, alliedMilitaryPower, Axis Powers]
-
A.
mainAlliedPower
Indicates that an entity serves as a primary or leading ally to another entity within an alliance or coalition.
-
B.
alliedCountries
Indicates that two countries are formally cooperating as allies, typically through mutual support agreements or shared strategic interests.
-
C.
alliedGovernment
Indicates that one government maintains a formal alliance or cooperative political relationship with another government.
-
D.
alliedForces
chosen
Indicates that multiple entities are cooperating militarily or strategically as part of the same alliance or coalition.
-
E.
majorAllies
Indicates that the entities are principal or primary allies, signifying a strong, significant, and mutually supportive alliance between them.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6695d19d48190b710de76e8666504 |
completed | May 2, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:07 p.m.