Triple
T1781218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lydian |
E39294
|
entity |
| Predicate | linguisticResearchField |
P29095
|
FINISHED |
| Object | Anatolian linguistics |
—
|
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: Anatolian linguistics | Statement: [Lydian, linguisticResearchField, Anatolian linguistics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linguisticResearchField Context triple: [Lydian, linguisticResearchField, Anatolian linguistics]
-
A.
linguisticField
chosen
Indicates that something pertains to or is associated with a particular area or subdiscipline within linguistics.
-
B.
hasLinguisticTypology
Indicates a relationship where a language or linguistic system is characterized by a specific typological classification or structural type.
-
C.
linguisticType
Indicates the type or category of language or linguistic system associated with an entity (e.g., spoken, signed, written, or other linguistic modality).
-
D.
linguisticClassification
Indicates the relationship by which an entity is categorized according to its language or linguistic type.
-
E.
linguisticArea
Indicates a regional context in which languages share features due to geographic proximity and contact rather than common genetic origin.
- 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab74dc9d1481908084ef07872a71f8 |
completed | March 7, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69aa61cf3ca881908641fd73ce2f7c9d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.