Triple
T26184597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMAS Adelaide (L01) |
E654789
|
entity |
| Predicate | canOperateLandingCraft |
P160025
|
FINISHED |
| Object | LHD Landing Craft (LLC) |
—
|
NE NERFINISHED |
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: LHD Landing Craft (LLC) | Statement: [HMAS Adelaide (L01), canOperateLandingCraft, LHD Landing Craft (LLC)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canOperateLandingCraft Context triple: [HMAS Adelaide (L01), canOperateLandingCraft, LHD Landing Craft (LLC)]
-
A.
hasLandingConditions
Indicates the specific conditions or requirements that must be met for a landing to occur or be permitted.
-
B.
landingCapability
Indicates the ability or suitability of an entity (e.g., a vehicle or system) to perform a landing under specified conditions.
-
C.
hasLandingCharacteristics
Indicates that an entity possesses specific attributes or features related to how it lands or is capable of landing.
-
D.
hasIslandLanding
Indicates that an entity includes or provides a designated landing area or facility located on an island.
-
E.
hasLandingFacilities
Indicates that a location or structure is equipped with facilities that allow aircraft or other vehicles to land there.
- 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_69f60c9d19748190b1e3405d56028876 |
completed | May 2, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 8:41 p.m.