Triple
T1197062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryukyuan languages |
E25690
|
entity |
| Predicate | ISO639FamilyCode |
P6290
|
FINISHED |
| Object | jpx |
—
|
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: jpx | Statement: [Ryukyuan languages, ISO639FamilyCode, jpx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO639FamilyCode Context triple: [Ryukyuan languages, ISO639FamilyCode, jpx]
-
A.
languageFamilyCode
chosen
Indicates the language family to which a given language belongs, represented by a standardized code.
-
B.
ISO639Macrolanguage
Indicates that a language variety is part of a broader ISO 639-defined macrolanguage grouping that encompasses multiple closely related individual languages.
-
C.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
D.
languageOfFamily
Indicates the language or languages commonly used or associated with a particular family.
-
E.
languageFamilyAssociated
Indicates that there is an association or connection between a language and a particular language family.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd9a305c819091513394f1b67784 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5d40a08190b7682d8ef8075421 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.