Triple
T26938543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prešernov trg |
E678450
|
entity |
| Predicate | namedAfterLanguage |
P167110
|
FINISHED |
| Object | Slovene |
—
|
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: Slovene | Statement: [Prešernov trg, namedAfterLanguage, Slovene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterLanguage Context triple: [Prešernov trg, namedAfterLanguage, Slovene]
-
A.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
B.
namedAfterSince
Indicates that one entity has borne the name of another entity starting from a specific point in time.
-
C.
alternateLanguageName
Indicates that an entity has an additional name or label in a different language from its primary or default name.
-
D.
usedAfterName
Indicates that one element is used or appears immediately after a name in some context or representation.
-
E.
usedAfterNameOf
Indicates that something is used immediately following the mention or specification of a name.
- 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_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 27, 2026, 6:17 a.m.