Triple
T15540572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nautilus (Fulton submarine) |
E370462
|
entity |
| Predicate | maximumSubmergedEndurance |
P57597
|
FINISHED |
| Object | about 1 hour (with compressed air) |
—
|
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 1 hour (with compressed air) | Statement: [Nautilus (Fulton submarine), maximumSubmergedEndurance, about 1 hour (with compressed air)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumSubmergedEndurance Context triple: [Nautilus (Fulton submarine), maximumSubmergedEndurance, about 1 hour (with compressed air)]
-
A.
timeInWater
Indicates the duration or amount of time that an entity spends in water.
-
B.
maximumDiveDepth
Indicates the greatest depth below the surface that an entity is capable of or allowed to dive.
-
C.
diveDuration
chosen
Indicates the length of time that a dive action or event lasts.
-
D.
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.
-
E.
speedSubmerged
Indicates the speed at which an entity moves while it is submerged in a fluid, typically underwater.
- 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.