Triple
T32055663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noric-Pannonian |
E818610
|
entity |
| Predicate | hasLanguageFamilyAssociation |
P36135
|
FINISHED |
| Object | Celtic languages |
—
|
NE NERFINISHED |
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: Celtic languages | Statement: [Noric-Pannonian, hasLanguageFamilyAssociation, Celtic languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageFamilyAssociation Context triple: [Noric-Pannonian, hasLanguageFamilyAssociation, Celtic languages]
-
A.
languageFamilyAssociated
Indicates that there is an association or connection between a language and a particular language family.
-
B.
languageFamilyAssociation
chosen
Indicates an association where one entity belongs to, is classified under, or is related to a particular language family.
-
C.
isInLanguageFamily
Indicates that a language belongs to, or is classified within, a particular language family based on shared linguistic ancestry or characteristics.
-
D.
inLanguageFamily
Indicates that two languages belong to the same linguistic family or classification.
-
E.
usesLanguageFamily
Indicates that an entity communicates or operates using a language that belongs to a specified 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
Created at: May 1, 2026, 12:21 a.m.