Triple
T34593923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loschwitzer Brücke |
E888258
|
entity |
| Predicate | hasRiverPiers |
P55979
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Loschwitzer Brücke, hasRiverPiers, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverPiers Context triple: [Loschwitzer Brücke, hasRiverPiers, no]
-
A.
hasPiersOn
Indicates that one structure or location is supported or extended by piers that are physically situated on another structure or surface.
-
B.
hasPier
Indicates that a location or structure possesses or includes a pier as part of its features.
-
C.
hasNumberOfPiersInWater
chosen
Indicates the quantity of piers that extend into or are situated within a body of water.
-
D.
numberOfPiers
Indicates the quantity of piers associated with or present in a given structure, location, or context.
-
E.
hasNearbyPier
Indicates that one entity is located close to a pier associated with or adjacent 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 1, 2026, 2:03 a.m.