Triple
T14864781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buda Castle Funicular lower station |
E349588
|
entity |
| Predicate | locatedOnEmbankment |
P27578
|
FINISHED |
| Object | Danube embankment |
—
|
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: Danube embankment | Statement: [Buda Castle Funicular lower station, locatedOnEmbankment, Danube embankment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnEmbankment Context triple: [Buda Castle Funicular lower station, locatedOnEmbankment, Danube embankment]
-
A.
locatedOnBankOfRiver
Indicates that one entity is situated along or directly adjacent to the bank of a specified river.
-
B.
hasEmbankment
chosen
Indicates that one entity possesses or is characterized by an embankment, such as a raised structure built to contain, support, or protect against water or terrain.
-
C.
locatedInHarbourArea
Indicates that something is situated within the geographic or administrative boundaries of a harbour area.
-
D.
locatedOnBuilding
Indicates that one entity is physically situated on the exterior or rooftop surface of a building.
-
E.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded574d0ec8190a6afed672ba6c2f9 |
completed | April 15, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:54 a.m.