Triple
T5898454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smith Island |
E131159
|
entity |
| Predicate | dialectDescribedAs |
P37438
|
FINISHED |
| Object | Elizabethan-influenced |
—
|
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: Elizabethan-influenced | Statement: [Smith Island, dialectDescribedAs, Elizabethan-influenced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dialectDescribedAs Context triple: [Smith Island, dialectDescribedAs, Elizabethan-influenced]
-
A.
regionalDialect
Indicates that one entity uses or is associated with a dialect specific to a particular geographic region in relation to another entity.
-
B.
majorDialectOf
Indicates that one dialect is the primary or most prominent dialect associated with a particular language or region.
-
C.
notableDialect
chosen
Indicates that an entity is recognized for having a distinct or noteworthy dialect associated with it.
-
D.
historicalDialect
Indicates that one dialect is a historically earlier or ancestral form of another dialect.
-
E.
partOfLinguisticVariety
Indicates that one linguistic variety (such as a dialect, register, or style) is a constituent or subset of another, broader linguistic variety.
- 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_69c00857439c819095950754176aa58a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0334dc8248190b7394dcece362d52 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:58 p.m.