Triple
T4333861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Jersey Channel |
E97416
|
entity |
| Predicate | dredgedToDepth |
P31148
|
FINISHED |
| Object | approximately 50 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 50 feet | Statement: [Port Jersey Channel, dredgedToDepth, approximately 50 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dredgedToDepth Context triple: [Port Jersey Channel, dredgedToDepth, approximately 50 feet]
-
A.
isDredged
chosen
Indicates that a waterway, channel, or seabed area has been excavated or cleared of sediment or debris, typically to maintain or increase its depth for navigation or other uses.
-
B.
riverbedDepth
Indicates the depth or vertical distance from the water surface to the bottom of a river at a given location or time.
-
C.
seaDepth
Indicates the measured vertical distance from the sea surface down to the seafloor at a given location.
-
D.
oceanDepthBelow
Indicates that one location or point in the ocean is situated at a greater depth (deeper below the surface) than another.
-
E.
hasWaterDepthCategory
Indicates the classification of something based on the range or category of its water depth.
- 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_69b3454662a481908fbcd0bbfaa3a0a4 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351516d488190b5b3d1936e3a325d |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4e13fc8190a42c519f37959d27 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:13 p.m.