Triple
T13602739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Navy Carrier Strike Group |
E324983
|
entity |
| Predicate | CSG21DeploymentYear |
P48905
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [Royal Navy Carrier Strike Group, CSG21DeploymentYear, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CSG21DeploymentYear Context triple: [Royal Navy Carrier Strike Group, CSG21DeploymentYear, 2021]
-
A.
deploymentYear
chosen
Indicates the calendar year in which an entity (such as a system, product, or resource) was first put into active use or operation.
-
B.
depositionYear
Indicates the calendar year in which something (such as a document, sample, or item) was formally deposited or submitted.
-
C.
commissionedYear
Indicates the year in which something (typically a work, project, or item) was formally ordered, authorized, or put into production.
-
D.
commissioningYearUnit1
Indicates the time unit (e.g., year, month) used to express the commissioning year of the first unit.
-
E.
emergenceYear
Indicates the calendar year in which something first appeared, originated, or came into existence.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae1b3ee481909bd43ded6227a3e5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.