Triple
T25823598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kärntnertor district |
E650464
|
entity |
| Predicate | gateConnectedTo |
P37306
|
FINISHED |
| Object | city fortifications of Vienna |
—
|
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: city fortifications of Vienna | Statement: [Kärntnertor district, gateConnectedTo, city fortifications of Vienna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gateConnectedTo Context triple: [Kärntnertor district, gateConnectedTo, city fortifications of Vienna]
-
A.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
B.
hasFareGateConnectionTo
Indicates that there is a direct passage or connection between two areas that is controlled or mediated by fare gates.
-
C.
connectsUnder
Indicates that one entity forms a connection to another entity by passing beneath or under it.
-
D.
connectsTerminus
Indicates that one entity serves as a terminus that is directly linked or joined to another entity.
-
E.
connectionTo
chosen
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60192afc881908dd64d8024d75329 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:31 a.m.