Triple
T3069234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockingham |
E62178
|
entity |
| Predicate | hasNearbyNavalBase |
P26804
|
FINISHED |
| Object | HMAS Stirling on Garden Island |
—
|
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: HMAS Stirling on Garden Island | Statement: [Rockingham, hasNearbyNavalBase, HMAS Stirling on Garden Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyNavalBase Context triple: [Rockingham, hasNearbyNavalBase, HMAS Stirling on Garden Island]
-
A.
hasNavalFacility
Indicates that one entity possesses, hosts, or contains a naval facility (such as a naval base, port, or installation) associated with it.
-
B.
hasNearbyHarbor
Indicates that one location has a harbor situated close to it in geographic proximity.
-
C.
hasNavalComponent
Indicates that something includes, involves, or is associated with a naval or maritime element as part of its composition or structure.
-
D.
hasMilitaryBase
Indicates that one entity possesses, hosts, or contains a military base associated with or located on another entity.
-
E.
hasNearbyBase
chosen
Indicates that one entity has a base or facility located in close physical proximity to another entity or location.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada0ffcc208190962cc9edcbf43c31 |
completed | March 8, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69ad9624b7a0819091d255614f5819ea |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.