Triple
T32021051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 21 frigate |
E817689
|
entity |
| Predicate | firstCommissionedUnit |
—
|
GENERATED |
| Object | HMS Amazon |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCommissionedUnit Context triple: [Type 21 frigate, firstCommissionedUnit, HMS Amazon]
-
A.
commissionedFirstUnit
chosen
Indicates that one entity formally brought the first operational unit of another entity into active service or use.
-
B.
firstCommissioned
Indicates that one entity was the first to formally authorize, request, or initiate the creation or execution of another entity.
-
C.
firstGeneratorCommissioned
Indicates that the first generator in a system or facility has been officially put into operation or brought online.
-
D.
launchedFirstUnit
Indicates that one entity initiated and deployed the first unit of something (e.g., product, system, or mission) before any others.
-
E.
secondUnitCommissioned
Indicates that a second unit of something has been formally placed into active service or operation.
- F. None of above.
Provenance (1 batch)
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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:16 a.m.