Triple
T14304355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russky Island |
E354652
|
entity |
| Predicate | transportLinkType |
P113695
|
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: [Russky Island, transportLinkType, cable-stayed bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportLinkType Context triple: [Russky Island, transportLinkType, cable-stayed bridge]
-
A.
transportHubType
Indicates the specific category or kind of transport hub associated with an entity (e.g., airport, train station, bus terminal).
-
B.
transportationLinksTo
Indicates that there is a transportation connection or route enabling movement or travel between the two entities.
-
C.
transportDependency
Indicates that one entity’s ability to be transported or to function in transport depends on another entity or transport resource.
-
D.
transportConnectionTo
Indicates a relationship where one entity provides or participates in a means of transportation that connects or leads to another entity.
-
E.
transportInterface
Indicates a relationship where one entity serves as the medium or mechanism through which another entity is transported or conveyed.
- F. None of above. chosen
Provenance (4 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85afabe48190926d6098047f4bcf |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:12 a.m.