Triple
T8588562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armada svizra |
E203370
|
entity |
| Predicate | hasOfficialLanguageVariant |
P26955
|
FINISHED |
| Object | German: Schweizer Armee |
—
|
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: Schweizer Armee | Statement: [Armada svizra, hasOfficialLanguageVariant, German: Schweizer Armee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialLanguageVariant Context triple: [Armada svizra, hasOfficialLanguageVariant, German: Schweizer Armee]
-
A.
languageVariant
Indicates that one language is a variant, dialect, or localized form of another language.
-
B.
hasLanguageOfOfficialName
chosen
Indicates that an entity’s official name is expressed in a specified language.
-
C.
linguisticVariant
Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
-
D.
hasOfficialNameVariant
Indicates that an entity has an alternative official form or version of its name.
-
E.
hasRepresentativeLanguage
Indicates that an entity is associated with a language that serves as its primary or officially recognized means of representation or communication.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c5e8888190b721e791c449b0df |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.