Triple
T26087056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constantinople Conference (1876–1877) |
E658012
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century international relations event |
C51095
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: 19th-century international relations event Context triple: [Constantinople Conference (1876–1877), instanceOf, 19th-century international relations event]
-
A.
19th-century conflict
A 19th-century conflict is a large-scale military or political struggle occurring between 1800 and 1899, typically involving nation-states or empires and shaped by industrialization, nationalism, and shifting imperial ambitions.
-
B.
18th-century event
An 18th-century event is a historically significant occurrence between 1701 and 1800 that reflects the political, social, cultural, or technological developments of that period.
-
C.
19th-century art event
A 19th-century art event is a historically situated gathering, exhibition, or performance in the 1800s where artworks were presented, debated, or experienced within the cultural and social context of the time.
-
D.
20th-century historical event
A 20th-century historical event is a significant occurrence between 1900 and 1999 that influenced political, social, economic, or cultural developments on a regional or global scale.
-
E.
19th-century controversy
A 19th-century controversy is a significant public dispute or prolonged debate during the 1800s, often involving social, political, scientific, or religious issues that shaped contemporary thought and policy.
- F. None of above. chosen
Provenance (1 batch)
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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:43 p.m.