Triple
T31759332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Hunyadi |
E810637
|
entity |
| Predicate | roseToProminenceThrough |
P104996
|
FINISHED |
| Object | military leadership |
—
|
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: military leadership | Statement: [House of Hunyadi, roseToProminenceThrough, military leadership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roseToProminenceThrough Context triple: [House of Hunyadi, roseToProminenceThrough, military leadership]
-
A.
roseToProminenceIn
Indicates the time or context in which an entity became widely recognized, influential, or notable.
-
B.
roseToProminenceUnder
Indicates that an entity became well-known, influential, or successful during the period of another entity’s leadership, guidance, or dominance.
-
C.
roseToPowerThrough
chosen
Indicates the means, process, or circumstances by which an entity gained authority, control, or a dominant position.
-
D.
ascendedTo
Indicates that one entity rose, climbed, or moved upward to reach the position, level, or location of another entity.
-
E.
gainedProminenceUnder
Indicates that an entity rose to greater importance, influence, or recognition during the leadership, authority, or period associated with 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab7ee7248190888c22161b3ce235 |
completed | May 3, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:30 p.m.