Triple
T20490510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German submarine U-75 |
E502729
|
entity |
| Predicate | rangeSurfaced_nm |
P26442
|
FINISHED |
| Object | 8700 at 10 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: 8700 at 10 kn | Statement: [German submarine U-75, rangeSurfaced_nm, 8700 at 10 kn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeSurfaced_nm Context triple: [German submarine U-75, rangeSurfaced_nm, 8700 at 10 kn]
-
A.
surfaceCover
Indicates that one entity forms the material or layer that covers the outer surface of another entity.
-
B.
hasSurfaceLevel
Indicates that one entity possesses or is characterized by a particular degree or measure of surface level (e.g., depth, detail, or superficiality).
-
C.
surfaceAccess
Indicates that one entity provides a means for another entity to reach, enter, or interact with a surface or outer layer.
-
D.
capSurface
Indicates that one entity serves as the top or end surface (a cap) enclosing or terminating another entity.
-
E.
rangeSize
chosen
Indicates the extent or magnitude of the range over which something applies, varies, or is distributed.
- 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.