Triple
T213526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corsicans |
E4767
|
entity |
| Predicate | historicalLanguageInfluence |
P4183
|
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: [Corsicans, historicalLanguageInfluence, Tuscan dialect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalLanguageInfluence Context triple: [Corsicans, historicalLanguageInfluence, Tuscan dialect]
-
A.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another language.
-
B.
influencedLanguage
chosen
Indicates that one language has had an effect on the development, structure, or usage of another language.
-
C.
historicalLanguageStatus
Indicates that a language had a particular official, social, or functional status during a past historical period.
-
D.
heritageLanguage
Indicates that one entity is the ancestral or culturally inherited language associated with another entity.
-
E.
historicallySpokenIn
Indicates that a language was used for spoken communication in a particular place or region during a past historical period.
- 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c32ae208190a03d504ef43ea659 |
completed | Feb. 28, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69a25b509400819093a6c1a1bac861e3 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.