Triple
T2893156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sorbian languages |
E63873
|
entity |
| Predicate | ISO639CollectiveCode |
P43831
|
FINISHED |
| Object | wen |
—
|
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: wen | Statement: [Sorbian languages, ISO639CollectiveCode, wen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO639CollectiveCode Context triple: [Sorbian languages, ISO639CollectiveCode, wen]
-
A.
ISO639Scope
Indicates the classification of a language according to its scope, such as whether it represents an individual language, a macrolanguage, or a collection of languages.
-
B.
ISO639-3CodeOfLanguage
Indicates that one entity is the ISO 639-3 three-letter language code assigned to the language represented by the other entity.
-
C.
sharesISO639-3CodeWith
Indicates that two language entities share the same ISO 639-3 code, meaning they are treated as the same language in that coding system.
-
D.
ISO639Macrolanguage
Indicates that a language variety is part of a broader ISO 639-defined macrolanguage grouping that encompasses multiple closely related individual languages.
-
E.
ISO639Status
Indicates the classification of a language’s status according to the ISO 639 standard (e.g., whether and how it is recognized or coded in that system).
- F. None of above. chosen
Provenance (4 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe062234c81909411e34db7d2683d |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd17bcdc8190aa47274a50ba4ad4 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde0f4c648190b9812e64f30c39da |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 10:07 p.m.