Triple
T28257789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yangshan Deep-Water Port |
E712497
|
entity |
| Predicate | hasBridgeLength |
P46595
|
FINISHED |
| Object | approximately 32.5 kilometers for Donghai 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: approximately 32.5 kilometers for Donghai Bridge | Statement: [Yangshan Deep-Water Port, hasBridgeLength, approximately 32.5 kilometers for Donghai Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBridgeLength Context triple: [Yangshan Deep-Water Port, hasBridgeLength, approximately 32.5 kilometers for Donghai Bridge]
-
A.
bridgeLength
chosen
Indicates the physical length or span of a bridge structure.
-
B.
hasSkyBridgeLength
Indicates the length measurement of a sky bridge connecting two structures or areas.
-
C.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
D.
hasNumberOfBridges
Indicates the quantitative relationship specifying how many bridges are associated with a given entity.
-
E.
hasBridgeSection
Indicates that one entity includes or is associated with a specific bridge section as a distinct part or component.
- 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_69efb5207eb08190827e4c34048030b1 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 11:09 p.m.