Triple
T16998665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pittsburgh Agreement |
E412382
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Czechoslovak independence document |
C531
|
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: Czechoslovak independence document Context triple: [Pittsburgh Agreement, instanceOf, Czechoslovak independence document]
-
A.
Czechoslovak legal decree
A Czechoslovak legal decree is a formal, state-issued legal act or regulation that had the force of law in Czechoslovakia, typically used to implement, interpret, or modify existing legislation or policy.
-
B.
Slovak national movement
The Slovak national movement was a 19th- and early 20th-century political, cultural, and social effort by Slovaks to assert their national identity, language, and autonomy within the multiethnic Habsburg and later Czechoslovak states.
-
C.
Lithuanian historical document
A Lithuanian historical document is an original or reproduced written, printed, or otherwise recorded source created in or about Lithuania’s past, providing evidence of historical events, governance, culture, or social life.
-
D.
founding document
chosen
A founding document is an authoritative text that formally establishes an organization, institution, or state by defining its core principles, structure, and governing rules.
-
E.
Polish historical document
A Polish historical document is an original or reproduced written, printed, or otherwise recorded source created in or about Poland’s past, providing evidence and context for historical events, people, institutions, or cultural practices.
- F. None of above.
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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:32 a.m.