Triple
T27201369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMAS Watson |
E683743
|
entity |
| Predicate | locatedInMilitaryBranch |
P91149
|
FINISHED |
| Object | Royal Australian Navy |
—
|
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: Royal Australian Navy | Statement: [HMAS Watson, locatedInMilitaryBranch, Royal Australian Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInMilitaryBranch Context triple: [HMAS Watson, locatedInMilitaryBranch, Royal Australian Navy]
-
A.
hasMilitaryBranch
Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
-
B.
militaryBranchAssociatedWith
chosen
Indicates a relationship where an entity is connected to, or operates as part of, a specific branch of a military organization.
-
C.
militaryBranchDomain
Indicates that one entity serves as the military branch or armed forces component associated with the domain, jurisdiction, or organizational scope of another entity.
-
D.
placeOfMilitaryService
Indicates the location or institution where a person performed their military service.
-
E.
militaryBranchEligibility
Indicates that an entity meets the required conditions to serve in a specified branch of the military.
- 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_69eefad1fd5c8190a4a46ea6afe58bfa |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: April 27, 2026, 9:36 a.m.