Triple
T7502366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neu-Ulm |
E177294
|
entity |
| Predicate | locatedOppositeBankOf |
P382
|
FINISHED |
| Object | Ulm across the Danube |
—
|
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: Ulm across the Danube | Statement: [Neu-Ulm, locatedOppositeBankOf, Ulm across the Danube]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOppositeBankOf Context triple: [Neu-Ulm, locatedOppositeBankOf, Ulm across the Danube]
-
A.
oppositeBankCity
Indicates that one city is located on the opposite bank of a river from another city.
-
B.
hasLandmarkOnBank
Indicates that a landmark is located on the bank (shore or edge) of a geographic feature such as a river, lake, or canal.
-
C.
locatedAcrossRiverFrom
chosen
Indicates that one entity is situated on the opposite side of a river relative to another entity.
-
D.
opposingLocation
Indicates that two entities are located directly opposite each other, typically across a defined reference such as a street, corridor, or boundary.
-
E.
locatedOnBankOfRiver
Indicates that one entity is situated along or directly adjacent to the bank of a specified river.
- 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_69c69f2696688190915a8458f2398211 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f81b431481908214b69c6c8d83bc |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d266d88190982cf5d2ee2e9564 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:44 p.m.