Triple
T17076319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prague Slavic Congress of 1848 |
E414355
|
entity |
| Predicate | subevent |
P60679
|
FINISHED |
| Object | formation of three national sections |
—
|
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: formation of three national sections | Statement: [Prague Slavic Congress of 1848, subevent, formation of three national sections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subevent Context triple: [Prague Slavic Congress of 1848, subevent, formation of three national sections]
-
A.
alternativeEvent
Indicates that one event serves as an alternative or substitute option to another event within the same context.
-
B.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
C.
subtheme
Indicates that one topic or concept functions as a more specific, subordinate theme within a broader overarching theme.
-
D.
specialtyEvent
Indicates that an event is designated as a special or distinctive occurrence, often differing from regular or routine events in nature or purpose.
-
E.
notableSubevent
chosen
Indicates that one event is a particularly significant or noteworthy component within a larger, encompassing 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc559388190b685504cca6ed62b |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.