Triple
T25465756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Hungarian Republic |
E638166
|
entity |
| Predicate | eventPrecedingFormation |
P42309
|
FINISHED |
| Object | Aster Revolution |
—
|
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: Aster Revolution | Statement: [First Hungarian Republic, eventPrecedingFormation, Aster Revolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventPrecedingFormation Context triple: [First Hungarian Republic, eventPrecedingFormation, Aster Revolution]
-
A.
eventBefore
chosen
Indicates that one event occurs earlier in time than another event.
-
B.
stateBeforeFormation
Indicates a relationship where one state or condition existed prior to the formation or creation of another entity or state.
-
C.
heirBeforeEvent
Indicates that one entity is designated as the heir of another prior to a specified event occurring.
-
D.
onFormation
Indicates that one entity is located on or attached to the surface of a formation (such as a geological or structural feature).
-
E.
heldBefore
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f74c5df88190a683cddba03a7afe |
completed | May 2, 2026, 1:08 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:14 p.m.