Triple
T35108377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U-703 |
E1013215
|
entity |
| Predicate | rangeSubmerged |
P140286
|
FINISHED |
| Object | 80 nmi at 4 kn |
—
|
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: 80 nmi at 4 kn | Statement: [U-703, rangeSubmerged, 80 nmi at 4 kn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeSubmerged Context triple: [U-703, rangeSubmerged, 80 nmi at 4 kn]
-
A.
rangeSubmerged_nm
chosen
Indicates the distance, measured in nautical miles, over which something remains submerged or underwater.
-
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.
submerged
Indicates that one entity is located beneath the surface of a liquid or other surrounding medium, typically fully covered by it.
-
D.
submergedForPurpose
Indicates that one entity is intentionally placed or kept under a liquid or surface in order to achieve a specific purpose or outcome.
-
E.
displacementSubmerged
Indicates the amount of fluid displaced by an object when it is submerged.
- 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_69f76dd659d08190bcdc00d37caafb62 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.