Triple
T24229627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HNLMS Karel Doorman (aircraft carrier) |
E601691
|
entity |
| Predicate | commissionedInRoyalNetherlandsNavy |
P150871
|
FINISHED |
| Object | 1948 |
—
|
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: 1948 | Statement: [HNLMS Karel Doorman (aircraft carrier), commissionedInRoyalNetherlandsNavy, 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissionedInRoyalNetherlandsNavy Context triple: [HNLMS Karel Doorman (aircraft carrier), commissionedInRoyalNetherlandsNavy, 1948]
-
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.
RoyalNavyDesignation
Indicates that an entity has been assigned an official designation or identifier by the Royal Navy.
-
D.
commissionedIn
Indicates that an entity was formally requested or authorized to be created, produced, or carried out in a specific time period or location.
-
E.
shipCommissionedDate
chosen
Indicates the date on which a ship was officially commissioned into 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f287e214e88190bf6d5b0f5f489f73 |
completed | April 29, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:01 a.m.