Triple
T33980938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daring-class destroyer |
E871279
|
entity |
| Predicate | RoyalAustralianNavyShip |
P177076
|
FINISHED |
| Object | HMAS Voyager |
—
|
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: HMAS Voyager | Statement: [Daring-class destroyer, RoyalAustralianNavyShip, HMAS Voyager]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RoyalAustralianNavyShip Context triple: [Daring-class destroyer, RoyalAustralianNavyShip, HMAS Voyager]
-
A.
navalClassNameInRoyalAustralianNavy
Indicates that a given naval class name is the designation used for that class within the Royal Australian Navy.
-
B.
RoyalNavyDesignation
Indicates that an entity has been assigned an official designation or identifier by the Royal Navy.
-
C.
isWarshipOf
chosen
Indicates that a given warship belongs to, is operated by, or is part of the naval forces of a specified country or organization.
-
D.
commissionedShip
Indicates that a ship has been formally placed into active service, typically following its construction or acquisition.
-
E.
BritishShipType
Indicates that the entity is classified as a type of ship associated with Britain, typically by origin, design, or service.
- 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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:50 a.m.