Triple
T6487350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tshiguvhu |
E146545
|
entity |
| Predicate | hasISO639-3CodeOfParentLanguage |
P8719
|
FINISHED |
| Object | ven |
—
|
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: ven | Statement: [Tshiguvhu, hasISO639-3CodeOfParentLanguage, ven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISO639-3CodeOfParentLanguage Context triple: [Tshiguvhu, hasISO639-3CodeOfParentLanguage, ven]
-
A.
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.
-
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.
ISO639Macrolanguage
Indicates that a language variety is part of a broader ISO 639-defined macrolanguage grouping that encompasses multiple closely related individual languages.
-
D.
ISO639-6Code
Indicates the standardized ISO 639-6 four-letter code that uniquely identifies a specific language variety or dialect.
-
E.
hasISO6393Code
chosen
Indicates that a language or linguistic entity is associated with a specific ISO 639-3 three-letter language code.
- 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_69c0090158c08190af0df9a2348d2d52 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a96a4048190a28dee5fd9258486 |
completed | March 22, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69c06740bebc81909d9d6956baa2bcb9 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:52 p.m.