Triple
T20490498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German submarine U-75 |
E502729
|
entity |
| Predicate | displacementSubmerged_tons |
P28075
|
FINISHED |
| Object | 857 |
—
|
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: 857 | Statement: [German submarine U-75, displacementSubmerged_tons, 857]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displacementSubmerged_tons Context triple: [German submarine U-75, displacementSubmerged_tons, 857]
-
A.
displacementSubmerged
chosen
Indicates the amount of fluid displaced by an object when it is submerged.
-
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.
standardDisplacement
Indicates the typical or officially specified amount of displacement (such as volume, weight, or capacity) associated with an entity under standard conditions.
-
E.
submergedPercentage
Indicates the proportion of an object’s total volume or height that is below the surface of a surrounding fluid or medium.
- 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.