Triple
T16478724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lanzo d’Intelvi |
E400257
|
entity |
| Predicate | usedLocalDialect |
P73137
|
FINISHED |
| Object | Lombard |
—
|
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: Lombard | Statement: [Lanzo d’Intelvi, usedLocalDialect, Lombard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedLocalDialect Context triple: [Lanzo d’Intelvi, usedLocalDialect, Lombard]
-
A.
usesLocalLanguageVariant
chosen
Indicates that an entity employs a region-specific or localized form of a language rather than a standard or global variant.
-
B.
regulatesDialect
Indicates a relationship in which one entity controls, shapes, or constrains the form, usage, or rules of a particular dialect.
-
C.
usesDialect
Indicates that one entity communicates or expresses itself using the specific dialect associated with another entity.
-
D.
focusesOnDialect
Indicates that the subject’s attention, work, or activity is specifically directed toward a particular dialect or set of dialects.
-
E.
dominantDialect
Indicates that one dialect is the primary or most influential form of a language within a particular context or region.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e01230881908b2147a25f78b7f4 |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:13 a.m.