Triple
T27820451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vella |
E702798
|
entity |
| Predicate | hasLocalNameInRomansh |
P6353
|
FINISHED |
| Object | Vella |
—
|
NE NERFINISHED |
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: Vella | Statement: [Vella, hasLocalNameInRomansh, Vella]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalNameInRomansh Context triple: [Vella, hasLocalNameInRomansh, Vella]
-
A.
hasNameInRomansh
Indicates that an entity is associated with a specific name or designation expressed in the Romansh language.
-
B.
hasNameInLocalLanguage
Indicates that an entity is associated with a name expressed in the local or native language of a given context or region.
-
C.
hasOfficialNameInRomansh
Indicates that an entity has an official name expressed in the Romansh language.
-
D.
hasLocalName
chosen
Indicates that an entity is known by a specific name or designation within a particular local language, script, or regional context.
-
E.
hasLocalNameFor
Indicates that one entity serves as the local or context-specific name or label used to refer to another entity.
- 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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 27, 2026, 5:48 p.m.