Triple
T25769419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temišvar |
E648976
|
entity |
| Predicate | belongsToToponymClass |
P82631
|
FINISHED |
| Object | Central European city exonyms |
—
|
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: Central European city exonyms | Statement: [Temišvar, belongsToToponymClass, Central European city exonyms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToToponymClass Context triple: [Temišvar, belongsToToponymClass, Central European city exonyms]
-
A.
hasTypeOfToponym
chosen
Indicates that one entity is classified as a specific type or category of toponym (place name) in relation to another entity.
-
B.
hasToponymicAssociation
Indicates a relationship where one entity is associated with, derived from, or named after a particular place or geographic name (toponym).
-
C.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of another entity.
-
D.
includesToponym
Indicates that one entity contains or references a place name (toponym) associated with another entity.
-
E.
hasToponymicQualifier
Indicates that an entity is associated with a specific place-related qualifier (toponym) used to distinguish it from other, similarly named entities.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 22, 2026, 5:13 a.m.