Triple
T7274916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMAS Stirling |
E162999
|
entity |
| Predicate | hasLogisticsRole |
P28699
|
FINISHED |
| Object | replenishment and resupply hub for Royal Australian Navy units |
—
|
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: replenishment and resupply hub for Royal Australian Navy units | Statement: [HMAS Stirling, hasLogisticsRole, replenishment and resupply hub for Royal Australian Navy units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLogisticsRole Context triple: [HMAS Stirling, hasLogisticsRole, replenishment and resupply hub for Royal Australian Navy units]
-
A.
hasCargoRole
Indicates that an entity participates in a cargo-related capacity or function within a transport, shipment, or logistics context.
-
B.
hasShipRole
Indicates that an entity holds or is assigned a specific role or function on a ship.
-
C.
logisticsFeature
chosen
Indicates that something possesses a characteristic, capability, or function specifically related to logistics operations or processes.
-
D.
hasCargoServices
Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
-
E.
logistics
Indicates the organization, coordination, and management of how resources, goods, or information are efficiently moved and handled between entities.
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:58 p.m.