Triple
T1692776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Alliance |
E36585
|
entity |
| Predicate | soughtToMaintain |
P31392
|
FINISHED |
| Object | balance of power in Europe |
—
|
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: balance of power in Europe | Statement: [Holy Alliance, soughtToMaintain, balance of power in Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soughtToMaintain Context triple: [Holy Alliance, soughtToMaintain, balance of power in Europe]
-
A.
maintainedFor
Indicates that something is kept in a particular state, condition, or operation for the benefit, use, or purpose of another entity.
-
B.
maintainedAs
Indicates that one entity is kept in a particular state, condition, or configuration by another entity through ongoing care, management, or support.
-
C.
maintainsTieWith
Indicates that one entity keeps an ongoing connection or relationship with another entity over time.
-
D.
retained
Indicates that one entity keeps possession, control, or continued engagement of another entity over a period of time.
-
E.
standardMaintained
Indicates that a specified standard is being upheld, preserved, or kept in compliance over time within the relevant context.
- F. None of above. chosen
Provenance (4 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69aa61b71cec8190b273588051058ebd |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69aaf33347e48190a32b6d0099e3d389 |
completed | March 6, 2026, 3:30 p.m. |
Created at: March 4, 2026, 7:29 p.m.