Triple
T15540573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nautilus (Fulton submarine) |
E370462
|
entity |
| Predicate | maximumSubmergedDepth |
P58244
|
FINISHED |
| Object | about 7 meters |
—
|
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 7 meters | Statement: [Nautilus (Fulton submarine), maximumSubmergedDepth, about 7 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumSubmergedDepth Context triple: [Nautilus (Fulton submarine), maximumSubmergedDepth, about 7 meters]
-
A.
maximumDiveDepth
chosen
Indicates the greatest depth below the surface that an entity is capable of or allowed to dive.
-
B.
submergedBy
Indicates that one entity is covered or overwhelmed by liquid, typically water, to the point of being beneath its surface due to the action or presence of another entity.
-
C.
maximumWaterDepth
Indicates the greatest depth of water present or allowed in a given context, such as a location, container, or body of water.
-
D.
depthBelowSurfaceInMeters
Indicates the vertical distance, measured in meters, that something is located below a reference surface level.
-
E.
maximumDepthBelowSeaLevel
Indicates the greatest vertical distance an entity extends or reaches below sea level.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04430b5188190a555a3cd4fb0c61c |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:07 a.m.