Triple
T8190912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weil am Rhein |
E191300
|
entity |
| Predicate | DreiländerbrückeConnectsTo |
P31305
|
FINISHED |
| Object | Huningue in France |
—
|
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: Huningue in France | Statement: [Weil am Rhein, DreiländerbrückeConnectsTo, Huningue in France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DreiländerbrückeConnectsTo Context triple: [Weil am Rhein, DreiländerbrückeConnectsTo, Huningue in France]
-
A.
linkedByFerryTo
Indicates that one place is connected to another by a ferry route that enables transport between them.
-
B.
hasNumberOfMainBridges
Indicates the quantity of primary or main bridges associated with a given entity.
-
C.
crossesStateBoundaryViaBridgeTo
Indicates that one entity crosses a state boundary to reach another entity specifically by traveling over a bridge.
-
D.
hasInternationalBridgeTo
chosen
Indicates a relationship where two locations are directly connected by a bridge that crosses an international border between them.
-
E.
CrimeanBridgeConnects
Indicates that the Crimean Bridge serves as a physical connection or link between two geographic locations.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4da2f4108190b9b69cb7f41ef374 |
completed | March 31, 2026, 4:29 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:41 p.m.