Triple
T1317444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuscans |
E28137
|
entity |
| Predicate | traditionalDialect |
P1762
|
FINISHED |
| Object | Tuscan 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: Tuscan dialect | Statement: [Tuscans, traditionalDialect, Tuscan dialect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalDialect Context triple: [Tuscans, traditionalDialect, Tuscan dialect]
-
A.
regionalDialect
chosen
Indicates that one entity uses or is associated with a dialect specific to a particular geographic region in relation to another entity.
-
B.
traditionalLanguageName
Indicates the name traditionally used in a particular language to refer to the subject entity.
-
C.
traditionalEnd
Indicates that one entity is the customary or historically established conclusion, outcome, or final stage of another entity or process.
-
D.
dominantDialect
Indicates that one dialect is the primary or most influential form of a language within a particular context or region.
-
E.
isTraditional
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
- 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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c175079481909077cf11ed72d6fa |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beebcb348190964bd7215811942c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.