Triple
T1199645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St George linkage subgroup |
E25749
|
entity |
| Predicate | evolvesVia |
P1245
|
FINISHED |
| Object | dialect continua |
—
|
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: dialect continua | Statement: [St George linkage subgroup, evolvesVia, dialect continua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evolvesVia Context triple: [St George linkage subgroup, evolvesVia, dialect continua]
-
A.
evolvedIn
Indicates that an entity originated or developed within a specified environment, context, or location over evolutionary time.
-
B.
futureEvolution
Indicates a predicted or potential future development or transformation of one entity into another.
-
C.
relatedSpeciesOrVariant
Indicates that one species or biological variant is taxonomically or genetically related to another.
-
D.
developedFrom
chosen
Indicates that one entity originates, evolves, or is derived from another as its source or precursor.
-
E.
typeSpecies
Indicates that a species is the designated type species that defines and anchors the taxonomic concept of a higher-level group (such as a genus).
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd9d56748190a12fe4a30346f1d8 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5ed2b88190aab992913957e1cf |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.