Triple
T27331273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Vampire |
E689804
|
entity |
| Predicate | RANService |
P162193
|
FINISHED |
| Object | served with distinction in the Royal Australian Navy |
—
|
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: served with distinction in the Royal Australian Navy | Statement: [HMS Vampire, RANService, served with distinction in the Royal Australian Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RANService Context triple: [HMS Vampire, RANService, served with distinction in the Royal Australian Navy]
-
A.
networkService
Indicates that one entity provides or participates in a network-based service or functionality for another entity or system.
-
B.
ranAs
Indicates that one entity previously operated or functioned in the role, capacity, or identity of another entity.
-
C.
enteredRAFService
Indicates that an entity began service in the Royal Air Force (RAF).
-
D.
inServiceFrom
Indicates the time or event from which an entity (such as a service, system, or asset) begins being operationally active or officially in use.
-
E.
operatesService
Indicates that an agent runs, manages, or provides a particular service.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f62acb65fc8190848dbe87124811ae |
completed | May 2, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 27, 2026, 11:38 a.m.