Triple
T30682568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vienna Literary Agreement |
E781093
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | language standardization agreement |
C3153
|
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: language standardization agreement Context triple: [Vienna Literary Agreement, instanceOf, language standardization agreement]
-
A.
normalization agreement
A normalization agreement is a formal contract between parties that establishes standardized terms, conditions, and procedures to ensure consistent, uniform handling of specific processes, data, or interactions.
-
B.
standardized language variety
A standardized language variety is a codified form of a language that has been deliberately regulated and accepted as the norm for public, official, and educational use within a speech community.
-
C.
language policy
Language policy is the set of deliberate decisions, principles, and regulations by which authorities or institutions influence the status, use, structure, and learning of one or more languages within a society.
-
D.
language standard annex
A language standard annex is a supplementary section of a programming language specification that defines optional, extended, or locale-specific features beyond the core standard.
-
E.
legal agreement
chosen
A legal agreement is a formally recognized arrangement between two or more parties that creates enforceable rights and obligations under the law.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:33 p.m.