Triple
T10630643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis II of Hungary |
E250442
|
entity |
| Predicate | significantEventAfterDeath |
P76982
|
FINISHED |
| Object | partition of Hungary between Habsburgs and Ottomans |
—
|
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: partition of Hungary between Habsburgs and Ottomans | Statement: [Louis II of Hungary, significantEventAfterDeath, partition of Hungary between Habsburgs and Ottomans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantEventAfterDeath Context triple: [Louis II of Hungary, significantEventAfterDeath, partition of Hungary between Habsburgs and Ottomans]
-
A.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
B.
namedAfterCauseOfDeath
Indicates that an entity is named after the cause of death of a person or organism.
-
C.
afterDeath
chosen
Indicates that one event, state, or condition occurs subsequent to and as a result of an entity’s death.
-
D.
endedActivityAfterDeathOf
Indicates that an activity was terminated following, and as a consequence of, the death of a specified entity.
-
E.
significantEventEnd
Indicates the point in time when a significant event or occurrence comes to a close or is considered finished.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df93a2b88190a0f3a52b8e88f54f |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:01 p.m.