Triple
T26938617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prešernov trg |
E678451
|
entity |
| Predicate | eponymBirthPlace |
P161340
|
FINISHED |
| Object | Vrba, Slovenia |
—
|
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: Vrba, Slovenia | Statement: [Prešernov trg, eponymBirthPlace, Vrba, Slovenia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eponymBirthPlace Context triple: [Prešernov trg, eponymBirthPlace, Vrba, Slovenia]
-
A.
eponymBirthName
Indicates that the object is the original birth name of the person or entity after whom something (the eponym) is named.
-
B.
eponymOriginCountry
Indicates the country from which the person or entity that gave its name (as an eponym) to something originates.
-
C.
eponymIsFrom
Indicates that the name of one entity is derived from or named after another entity.
-
D.
eponymKnownFor
Indicates that a person or entity is widely recognized or named as the source or inspiration for something else (such as a concept, place, or object).
-
E.
eponymCountry
Indicates that a country is named after (or serves as the namesake for) a particular person, place, or entity.
- F. None of above. chosen
Provenance (4 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62050af2481909ce5687b36c4aabc |
completed | May 2, 2026, 4:03 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 27, 2026, 6:17 a.m.