Triple
T30880384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saigon River Tunnel |
E786592
|
entity |
| Predicate | maximumDepthBelowWaterSurface |
P87151
|
FINISHED |
| Object | about 24 m |
—
|
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: about 24 m | Statement: [Saigon River Tunnel, maximumDepthBelowWaterSurface, about 24 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumDepthBelowWaterSurface Context triple: [Saigon River Tunnel, maximumDepthBelowWaterSurface, about 24 m]
-
A.
maximumWaterDepth
Indicates the greatest depth of water present or allowed in a given context, such as a location, container, or body of water.
-
B.
depthBelowSurfaceInMeters
chosen
Indicates the vertical distance, measured in meters, that something is located below a reference surface level.
-
C.
minimumWaterDepth
Indicates the smallest water depth at which the related object, activity, or condition is valid, safe, or applicable.
-
D.
maximumDepthBelowSeaLevel
Indicates the greatest vertical distance an entity extends or reaches below sea level.
-
E.
lakeMaximumDepth
Indicates the greatest recorded vertical distance from the lake’s surface to its deepest point.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 29, 2026, 8:48 p.m.