Triple
T28540660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pamphylian Greek |
E722280
|
entity |
| Predicate | hasDialectalGroup |
P1254
|
FINISHED |
| Object | Pamphylian dialect |
—
|
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: Pamphylian dialect | Statement: [Pamphylian Greek, hasDialectalGroup, Pamphylian dialect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDialectalGroup Context triple: [Pamphylian Greek, hasDialectalGroup, Pamphylian dialect]
-
A.
hasMajorDialectGroup
chosen
Indicates that an entity (typically a language) is associated with a primary or major dialect group to which it belongs.
-
B.
hasDialectContinuumWith
Indicates that two languages or dialects are part of a continuous chain of mutually intelligible varieties, without a clear boundary separating them.
-
C.
hasDialectalDifferenceWith
Indicates that two language varieties differ from each other in dialectal features such as pronunciation, vocabulary, or grammar.
-
D.
hasDialectalCounterpart
Indicates that one linguistic form has a corresponding equivalent or variant in another dialect.
-
E.
hasDialectalFeaturesSharedWith
Indicates that two language varieties share specific dialectal features or characteristics in common.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 28, 2026, 3:35 a.m.