Triple
T25908578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Curieux |
E652824
|
entity |
| Predicate | capturedAndCommissioned |
P159561
|
FINISHED |
| Object | Royal Navy warship |
—
|
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: Royal Navy warship | Statement: [HMS Curieux, capturedAndCommissioned, Royal Navy warship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capturedAndCommissioned Context triple: [HMS Curieux, capturedAndCommissioned, Royal Navy warship]
-
A.
shipCommissionedAs
Indicates that a ship entered active service under a specific name or designation at the time of its commissioning.
-
B.
commissionedShip
Indicates that a ship has been formally placed into active service, typically following its construction or acquisition.
-
C.
shipCommissionedDate
Indicates the date on which a ship was officially commissioned into service.
-
D.
firstCommissioned
Indicates that one entity was the first to formally authorize, request, or initiate the creation or execution of another entity.
-
E.
commissionedInService
Indicates that an entity was formally brought into active service or duty within a particular organization, role, or context.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603c15b348190a7f00745b6475b28 |
completed | May 2, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 8:28 a.m.