Triple
T28791898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kvarken Archipelago |
E726975
|
entity |
| Predicate | ReplotBridgeType |
P1787
|
FINISHED |
| Object | cable-stayed bridge |
—
|
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: cable-stayed bridge | Statement: [Kvarken Archipelago, ReplotBridgeType, cable-stayed bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ReplotBridgeType Context triple: [Kvarken Archipelago, ReplotBridgeType, cable-stayed bridge]
-
A.
bridgeType
chosen
Indicates the specific kind or classification of a bridge associated with an entity.
-
B.
originalBridgeRenamed
Indicates that a bridge has undergone a name change from its original designation to a new one.
-
C.
bridgeReplaced
Indicates that one bridge has been substituted or exchanged for another, typically as a result of construction, repair, or upgrade.
-
D.
bridgesStyleBetween
Indicates a relationship where something connects or harmonizes two different styles, serving as a transitional or integrative link between them.
-
E.
bridgeModel
Indicates a relationship where one entity serves as an intermediate model or representation that connects or translates between two other entities or systems.
- 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:23 a.m.