Triple
T30948797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steinway Tunnel |
E788474
|
entity |
| Predicate | connectsUnderwater |
P33993
|
FINISHED |
| Object | Manhattan and Queens beneath the East River |
—
|
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: Manhattan and Queens beneath the East River | Statement: [Steinway Tunnel, connectsUnderwater, Manhattan and Queens beneath the East River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsUnderwater Context triple: [Steinway Tunnel, connectsUnderwater, Manhattan and Queens beneath the East River]
-
A.
canBreatheUnderwater
Indicates that an entity has the ability to breathe while submerged in water without needing to surface for air.
-
B.
connectsUnder
chosen
Indicates that one entity forms a connection to another entity by passing beneath or under it.
-
C.
hasDeepDivingAbility
Indicates that an entity possesses the capability to dive to significant depths, typically beyond normal or shallow diving limits.
-
D.
connectsOcean
Indicates that one geographic entity serves as a link or passage between another entity and an ocean.
-
E.
submersibleName
Indicates that a submersible is identified by or associated with a specific name.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
Created at: April 29, 2026, 8:53 p.m.