Triple
T37371263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilna |
E927848
|
entity |
| Predicate | contrastsWithEndonym |
P186337
|
FINISHED |
| Object | Vilnius |
—
|
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: Vilnius | Statement: [Wilna, contrastsWithEndonym, Vilnius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contrastsWithEndonym Context triple: [Wilna, contrastsWithEndonym, Vilnius]
-
A.
endonymContrast
chosen
Indicates a contrast between an entity’s own local or native name (endonym) and another name or naming form used for it.
-
B.
contrastsWithMajorityLanguage
Indicates that one language or linguistic feature is notably different from, and stands in opposition to, the dominant or majority language in a given context.
-
C.
isNonEndonymFor
Indicates that a given name for a place, people, or language is used by outsiders and is not the name used by the group or locale itself.
-
D.
isEndonym
Indicates that a name is used by a group to refer to themselves or their own place/language, rather than being an external or foreign designation.
-
E.
hasEndonym
Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
- 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
Created at: May 3, 2026, 4:16 p.m.