Triple
T9955730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian People’s Army |
E195441
|
entity |
| Predicate | hadPoliticalDirectorate |
P60330
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hungarian People’s Army, hadPoliticalDirectorate, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPoliticalDirectorate Context triple: [Hungarian People’s Army, hadPoliticalDirectorate, yes]
-
A.
laterPoliticalCommissar
Indicates that the person served as a political commissar of the specified unit or organization at a later point in time (not necessarily their first or only such role).
-
B.
hasPoliticalBureau
chosen
Indicates that an entity possesses or is associated with a political bureau as part of its organizational or governance structure.
-
C.
militaryDirector
Indicates that one entity serves as the military director or chief military authority for another entity.
-
D.
headedPoliticallyBy
Indicates that one political entity serves as the governing authority or leadership over another entity.
-
E.
hadExecutivePowerIn
Indicates that an entity held executive authority or governing power within a specified organization, institution, or jurisdiction during a certain period.
- 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb69631d08190ab2b1d1c22d46da7 |
completed | April 2, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:46 p.m.