Triple
T8808195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsakonians |
E209586
|
entity |
| Predicate | languageTransmission |
P4292
|
FINISHED |
| Object | mainly older generations |
—
|
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: mainly older generations | Statement: [Tsakonians, languageTransmission, mainly older generations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageTransmission Context triple: [Tsakonians, languageTransmission, mainly older generations]
-
A.
languageOfTransmission
Indicates the language used to convey or transmit the content or information in a given communication or resource.
-
B.
languageOfTeachings
Indicates the language in which teachings, lessons, or instructional content are delivered or expressed.
-
C.
languageShift
chosen
Indicates a change in the primary language used by an entity, such as switching from one language to another over time or in a given context.
-
D.
languageOfCommunications
Indicates that a specified language is used as the medium for communications associated with an entity or interaction.
-
E.
textualTransmission
Indicates the transfer or communication of information through written or printed text from one source to another.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fd4cbec8190a929d4e60da8ad65 |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.