Triple
T24322586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russia and Prussia |
E613008
|
entity |
| Predicate | reorganizedAfterConflict |
P72851
|
FINISHED |
| Object | Congress of Vienna |
—
|
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: Congress of Vienna | Statement: [Russia and Prussia, reorganizedAfterConflict, Congress of Vienna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reorganizedAfterConflict Context triple: [Russia and Prussia, reorganizedAfterConflict, Congress of Vienna]
-
A.
postConflictReconstruction
Indicates efforts or processes aimed at rebuilding, restoring, and stabilizing societies, institutions, and infrastructure following the end of an armed conflict.
-
B.
conflictResolvedBy
Indicates that a conflict or dispute is settled or addressed through the actions, decisions, or intervention of a specified entity or process.
-
C.
reorganizedDueTo
chosen
Indicates that one entity was reorganized as a consequence of, or in response to, another specified factor, event, or condition.
-
D.
conflictRecognized
Indicates that a conflict between parties, interests, or actions has been identified and acknowledged.
-
E.
reorganizedIn
Indicates that an entity underwent a structural or organizational change within a specified context, time, or framework.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292ad4cc881908794b501cf70b7a1 |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:52 a.m.