Triple

T26184595
Position Surface form Disambiguated ID Type / Status
Subject HMAS Adelaide (L01) E654789 entity
Predicate vehicleDeckCapacity P161263 FINISHED
Object armoured vehicles and trucks 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: armoured vehicles and trucks | Statement: [HMAS Adelaide (L01), vehicleDeckCapacity, armoured vehicles and trucks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: vehicleDeckCapacity
Context triple: [HMAS Adelaide (L01), vehicleDeckCapacity, armoured vehicles and trucks]
  • A. cargoCapacityFeature
    Indicates that an entity has a feature specifying how much cargo it can carry or accommodate.
  • B. maximumPassengerCapacity
    Indicates the greatest number of passengers that an entity is designed or allowed to carry at one time.
  • C. designedCargoCapacity
    Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
  • D. transportCapacity
    Indicates the maximum quantity of people, goods, or materials that can be transported by an entity or system within a given operation or time frame.
  • E. cargoCapacityConfigurable
    Indicates that the cargo capacity of an entity can be adjusted or configured rather than being fixed.
  • 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_69ee5b469bc081908fe486453fdad810 completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69f6135293908190809e255bf6334760 completed May 2, 2026, 3:08 p.m.
PD Predicate disambiguation batch_69f611a9272881909093360472be832c completed May 2, 2026, 3 p.m.
PDg Predicate description generation batch_69f6125e54e0819088ee33a20efcc9e6 completed May 2, 2026, 3:03 p.m.
Created at: April 26, 2026, 8:41 p.m.