Triple
T8265086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gothic alphabet |
E193280
|
entity |
| Predicate | usedForLanguageStatus |
P25828
|
FINISHED |
| Object | extinct language |
—
|
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: extinct language | Statement: [Gothic alphabet, usedForLanguageStatus, extinct language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForLanguageStatus Context triple: [Gothic alphabet, usedForLanguageStatus, extinct language]
-
A.
usedInLanguage
Indicates that something (such as a word, expression, or symbol) is employed or occurs within a particular language.
-
B.
hasLanguageStatus
chosen
Indicates that an entity has a particular status or condition regarding its language use, recognition, or classification.
-
C.
usesWorkingLanguagesOf
Indicates that one entity employs or operates using the working languages associated with another entity.
-
D.
languageStatusSource
Indicates the source or authority from which the information about a language’s status is derived.
-
E.
ethnicLanguageStatus
Indicates the status or role of a language in relation to a particular ethnic group (e.g., primary, secondary, heritage, or minority language).
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb794c54448190a685b8d0070980d7 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:50 p.m.