Triple
T6580765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Epistle to John Rankine |
E157288
|
entity |
| Predicate | writtenInDialect |
P12727
|
FINISHED |
| Object | Scots dialect |
—
|
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: Scots dialect | Statement: [The Epistle to John Rankine, writtenInDialect, Scots dialect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenInDialect Context triple: [The Epistle to John Rankine, writtenInDialect, Scots dialect]
-
A.
notableDialect
Indicates that an entity is recognized for having a distinct or noteworthy dialect associated with it.
-
B.
majorDialectOf
Indicates that one dialect is the primary or most prominent dialect associated with a particular language or region.
-
C.
writtenIn
chosen
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
D.
regionalDialect
Indicates that one entity uses or is associated with a dialect specific to a particular geographic region in relation to another entity.
-
E.
writtenInCountry
Indicates that a written work was created, authored, or composed within the geographical boundaries of a specific country.
- 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_69c6882b3a108190b3a9eb343ae4162c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c07cdf048190945ca5810fb1de88 |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6acfb462481909cb7aff5af4bca9d |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:54 p.m.