Triple
T19096973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vrakuňa |
E467430
|
entity |
| Predicate | incorporatedIntoBratislavaIn |
P134354
|
FINISHED |
| Object | 1972 |
—
|
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: 1972 | Statement: [Vrakuňa, incorporatedIntoBratislavaIn, 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incorporatedIntoBratislavaIn Context triple: [Vrakuňa, incorporatedIntoBratislavaIn, 1972]
-
A.
incorporatedIntoVienna
Indicates that one entity (typically a place or administrative unit) has been formally merged into and made part of the city of Vienna.
-
B.
countryAfter1918
Indicates that the entity functioned as a country or sovereign state at some point after the year 1918.
-
C.
countryBefore1918
Indicates that one country existed or held a particular status prior to the year 1918 in relation to another country or temporal reference.
-
D.
capitalDuringAustrianRule
Indicates that a place served as the capital of a territory or region specifically during the period of Austrian rule.
-
E.
countryDuringAustriaHungaryPeriod
Indicates that an entity functioned as a country or territorial unit during the historical period when Austria-Hungary existed.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e369aeac81908913c21f4c234c8e |
completed | April 20, 2026, 8:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.