Triple
T13505025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tk (macrolanguage) |
E320993
|
entity |
| Predicate | isLivingLanguage |
P20092
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [tk (macrolanguage), isLivingLanguage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLivingLanguage Context triple: [tk (macrolanguage), isLivingLanguage, true]
-
A.
isWorkingLanguageOf
Indicates that a particular language is officially used as a medium of work, communication, or operation within a specified organization, institution, or context.
-
B.
extantLanguage
chosen
Indicates that a language currently exists or is in active use, as opposed to being extinct or only historically attested.
-
C.
isWidelySpokenIn
Indicates that a language is spoken by a large portion of the population across many regions or communities within a specified area.
-
D.
ethnicLanguageStatus
Indicates the status or role of a language in relation to a particular ethnic group (e.g., primary, secondary, heritage, or minority language).
-
E.
isScheduledLanguageOf
Indicates that a particular language is officially planned or designated to be used for a specific event, program, or context.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf810e248190a060481004503f96 |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.