Triple
T14629619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chelsea Street Bridge |
E343443
|
entity |
| Predicate | hasNavigationChannelWidth |
P25021
|
FINISHED |
| Object | approximately 250 feet |
—
|
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 250 feet | Statement: [Chelsea Street Bridge, hasNavigationChannelWidth, approximately 250 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavigationChannelWidth Context triple: [Chelsea Street Bridge, hasNavigationChannelWidth, approximately 250 feet]
-
A.
hasNavigationArea
Indicates that an entity is associated with or includes a designated area intended for navigation or movement.
-
B.
maximumChannelWidth
chosen
Indicates the greatest allowable or observed width of a channel in the given context.
-
C.
hasNavigationSpan
Indicates that one entity includes or is associated with a specific navigational range or segment used for movement or routing.
-
D.
hasNavigationCharacteristic
Indicates that an entity possesses a specific property, feature, or quality related to navigation or navigational behavior.
-
E.
naveWidth
Indicates the width measurement of a building’s nave in a spatial or architectural context.
- 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4a7c8fc81909d10c1f563d7d1e7 |
completed | April 14, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69de657359c88190b082e3e9f86fc1d7 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:26 a.m.