Triple
T4759978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omicron |
E105675
|
entity |
| Predicate | languageFamilyUsage |
P36135
|
FINISHED |
| Object | Hellenic languages |
—
|
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: Hellenic languages | Statement: [Omicron, languageFamilyUsage, Hellenic languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageFamilyUsage Context triple: [Omicron, languageFamilyUsage, Hellenic languages]
-
A.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
B.
languageFamilyOf
Indicates that one entity is the language family to which the other entity (a specific language) belongs.
-
C.
languageFamilyDominant
Indicates that one language family holds a primary or prevailing status over others within a given context (such as a region, population, or system).
-
D.
languageFamilyAssociation
chosen
Indicates an association where one entity belongs to, is classified under, or is related to a particular language family.
-
E.
languageFamilyStatus
Indicates the classification or recognition status of a language within a particular language family (e.g., primary, branch, extinct, or disputed).
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650dc7fc81909b483ef3c456ae0d |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.