Triple
T5153433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prešporok |
E116250
|
entity |
| Predicate | usedPrimarilyBefore |
P7341
|
FINISHED |
| Object | official adoption of the name Bratislava |
—
|
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: official adoption of the name Bratislava | Statement: [Prešporok, usedPrimarilyBefore, official adoption of the name Bratislava]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPrimarilyBefore Context triple: [Prešporok, usedPrimarilyBefore, official adoption of the name Bratislava]
-
A.
usedPrimarilyIn
Indicates that something is mainly or most commonly employed within a particular context, domain, or purpose.
-
B.
usedBefore
chosen
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
-
C.
usedToBe
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
-
D.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
E.
primarilyUsedBy
Indicates that something is mainly or most commonly used by a particular entity or group.
- 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_69bd445d94788190b72e2cc563120995 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c1354c81908176703b4853c1a4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b0fbb88190851e2d7ae1bdcc09 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.