Triple
T30830534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treviolo |
E785202
|
entity |
| Predicate | hasLocalAdministrationLanguage |
P86356
|
FINISHED |
| Object | Italian |
—
|
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: Italian | Statement: [Treviolo, hasLocalAdministrationLanguage, Italian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalAdministrationLanguage Context triple: [Treviolo, hasLocalAdministrationLanguage, Italian]
-
A.
languageOfCurrentAdministration
Indicates the language currently used by the governing or administrative authority in charge.
-
B.
usesLanguageForAdministration
chosen
Indicates that an entity employs a particular language as the official medium for its administrative or governmental functions.
-
C.
hasLocalServicesLanguage
Indicates that the local services available in a given context operate or are provided using a specified language.
-
D.
isSpokenInAdministrativeUnit
Indicates that a particular language is used or officially spoken within a specified administrative unit or region.
-
E.
localLanguageStatus
Indicates the status or condition of a language as used within a specific local or regional context.
- 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: April 29, 2026, 8:44 p.m.