Triple
T29561111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Livonia Governorate |
E750040
|
entity |
| Predicate | eliteLanguage |
P119293
|
FINISHED |
| Object | German |
—
|
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: German | Statement: [Livonia Governorate, eliteLanguage, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eliteLanguage Context triple: [Livonia Governorate, eliteLanguage, German]
-
A.
eligibleLanguage
Indicates that a particular language satisfies the required conditions to be considered valid or allowed in a given context.
-
B.
languageOfExpression
Indicates that a particular language is used as the medium or form in which an expression (such as a text, utterance, or work) is realized.
-
C.
languageUse
Indicates the language or languages an entity uses for communication, expression, or interaction.
-
D.
hasEliteLanguage
chosen
Indicates that an entity uses or is associated with a language variety considered elite, prestigious, or high-status within a given context.
-
E.
capitalLanguage
Indicates that the specified language is the primary or official language used in the capital city of a given entity.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66d1ccf448190bf7c453e94a1fe17 |
completed | May 2, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 5:19 p.m.