Triple
T21237942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eperjes |
E523394
|
entity |
| Predicate | todayIdentifiedAs |
P45454
|
FINISHED |
| Object | city of Prešov in Slovakia |
—
|
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: city of Prešov in Slovakia | Statement: [Eperjes, todayIdentifiedAs, city of Prešov in Slovakia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: todayIdentifiedAs Context triple: [Eperjes, todayIdentifiedAs, city of Prešov in Slovakia]
-
A.
knownTodayAs
Indicates that an entity is currently referred to or recognized by a particular name or designation in the present time.
-
B.
modernIdentification
chosen
Indicates that one entity serves as the contemporary or currently accepted identification or classification of another entity.
-
C.
publiclyIdentifiesAs
Indicates that an entity openly declares or presents themself to others as having a particular identity or role.
-
D.
samePersonAs
Indicates that two referenced entities are in fact the very same individual, not just similar or related.
-
E.
typicalIdentity
Indicates that one entity is the standard, characteristic, or most representative identity of another entity within a given 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_69e0b513b89c81908b27147e91368db2 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735212ad4819082d85f4d4342faf9 |
completed | April 21, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:46 p.m.