Triple
T28800557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bailey Island Bridge |
E727217
|
entity |
| Predicate | engineeredTo |
P20750
|
FINISHED |
| Object | withstand strong tides and currents |
—
|
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: withstand strong tides and currents | Statement: [Bailey Island Bridge, engineeredTo, withstand strong tides and currents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineeredTo Context triple: [Bailey Island Bridge, engineeredTo, withstand strong tides and currents]
-
A.
engineeredForLabel
Indicates that something has been specifically designed, adapted, or optimized to serve, support, or be used for the referenced label or purpose.
-
B.
engineeredBy
Indicates that an entity has been designed, created, or developed through the technical work or expertise of another entity.
-
C.
designedToWithstand
chosen
Indicates that something has been intentionally created or engineered to resist, endure, or remain functional under specified conditions, forces, or stresses.
-
D.
isEngineeredStructure
Indicates that something is a man-made or artificially constructed structure, typically designed and built through engineering processes.
-
E.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of 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_69f0319b7c44819085736bcc256185e6 |
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:27 a.m.