Triple
T1272392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Pampanito |
E15737
|
entity |
| Predicate | displacementSubmerged |
P28075
|
FINISHED |
| Object | about 2,424 long tons |
—
|
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 2,424 long tons | Statement: [USS Pampanito, displacementSubmerged, about 2,424 long tons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displacementSubmerged Context triple: [USS Pampanito, displacementSubmerged, about 2,424 long tons]
-
A.
submerged
Indicates that one entity is located beneath the surface of a liquid or other surrounding medium, typically fully covered by it.
-
B.
submergedFeatures
Indicates that certain features or elements are located beneath the surface of a body of water or otherwise covered by liquid.
-
C.
displacementFullLoad
Indicates the total volume of water displaced by a vessel when it is fully loaded to its maximum operational capacity.
-
D.
sunk
Indicates that one entity caused another entity to go below the surface of a liquid, typically water, so that it is submerged or destroyed.
-
E.
displacement
Indicates a change in an entity’s position from one location to another, typically specifying both direction and magnitude of that movement.
- F. None of above. chosen
Provenance (4 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c06c033081909bc594157abaf5bb |
completed | March 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bfa205ec81909d8170b398345615 |
completed | March 1, 2026, 10:37 p.m. |
Created at: March 1, 2026, 7:50 p.m.