Triple
T20490509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German submarine U-75 |
E502729
|
entity |
| Predicate | maximumSubmergedSpeed_kn |
P71676
|
FINISHED |
| Object | 8.0 |
—
|
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: 8.0 | Statement: [German submarine U-75, maximumSubmergedSpeed_kn, 8.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumSubmergedSpeed_kn Context triple: [German submarine U-75, maximumSubmergedSpeed_kn, 8.0]
-
A.
speedSubmerged
chosen
Indicates the speed at which an entity moves while it is submerged in a fluid, typically underwater.
-
B.
maximumWaterSpeed_kmh
Indicates the highest speed, measured in kilometers per hour, at which an entity can move through water.
-
C.
maximumWaterSpeed
Indicates the highest speed an entity can move through water under specified conditions.
-
D.
diveSpeed
Indicates the speed at which an entity moves downward or descends, typically through a fluid such as air or water.
-
E.
maximumDiveDepth
Indicates the greatest depth below the surface that an entity is capable of or allowed to dive.
- 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_69e0b4b0373881909dd3e9387f82eab4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cb8e7848190a1dc497a10ae798c |
completed | April 20, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:35 a.m.