Triple
T7228675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canberra-class landing helicopter dock |
E154847
|
entity |
| Predicate | landingCraftCapacity |
P72527
|
FINISHED |
| Object | up to 4 LHD landing craft |
—
|
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: up to 4 LHD landing craft | Statement: [Canberra-class landing helicopter dock, landingCraftCapacity, up to 4 LHD landing craft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingCraftCapacity Context triple: [Canberra-class landing helicopter dock, landingCraftCapacity, up to 4 LHD landing craft]
-
A.
lifeboatCapacity
Indicates the maximum number of people or load that a lifeboat is designed and certified to safely carry.
-
B.
hasBoatCapacity
chosen
Indicates the maximum number of people or amount of load that a boat is designed or allowed to carry.
-
C.
shipLength
Indicates the physical length measurement of a ship.
-
D.
hasAmphibiousCapability
Indicates that an entity possesses the ability to operate effectively in both water and land environments.
-
E.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
- 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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6e9e0ba248190a57a3b4fa8b858c7 |
completed | March 27, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.