Triple
T15067987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BB-62 |
E379802
|
entity |
| Predicate | hasStandardDisplacement |
P10289
|
FINISHED |
| Object | about 45,000 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 45,000 long tons | Statement: [BB-62, hasStandardDisplacement, about 45,000 long tons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandardDisplacement Context triple: [BB-62, hasStandardDisplacement, about 45,000 long 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.
hasAmphibiousCapability
Indicates that an entity possesses the ability to operate effectively in both water and land environments.
-
C.
navalStandardType
Indicates the specific naval standard or classification system under which an entity (such as a vessel, equipment, or procedure) is defined or regulated.
-
D.
tonnageClass
Indicates a classification relationship where an entity is assigned to a category based on its tonnage (weight or carrying capacity range).
-
E.
hasMainBulkCargoPort
Indicates that an entity serves as the primary port used for handling bulk cargo for another entity.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dedeebc7e48190a86b4f0afe8844bb |
completed | April 15, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:02 a.m.