Triple
T21619217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forrest Sherman-class destroyer |
E533530
|
entity |
| Predicate | shipDisplacementStandard |
P10289
|
FINISHED |
| Object | approximately 4,050 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: approximately 4,050 tons | Statement: [Forrest Sherman-class destroyer, shipDisplacementStandard, approximately 4,050 tons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipDisplacementStandard Context triple: [Forrest Sherman-class destroyer, shipDisplacementStandard, approximately 4,050 tons]
-
A.
standardDisplacement
chosen
Indicates the typical or officially specified amount of displacement (such as volume, weight, or capacity) associated with an entity under standard conditions.
-
B.
shipLength
Indicates the physical length measurement of a ship.
-
C.
tonnageClass
Indicates a classification relationship where an entity is assigned to a category based on its tonnage (weight or carrying capacity range).
-
D.
maxVesselTonnage
Indicates the maximum tonnage capacity that a vessel is allowed or designed to carry.
-
E.
hullWeight_lb
Indicates the weight of a hull measured in pounds.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3bad094c8190879d4aef7988254a |
completed | April 27, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:34 p.m.