Triple
T36105491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Angeles class |
E1044341
|
entity |
| Predicate | lastCommissionedYear |
P112528
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Los Angeles class, lastCommissionedYear, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastCommissionedYear Context triple: [Los Angeles class, lastCommissionedYear, 1996]
-
A.
lastShipCommissioningDate
chosen
Indicates the date on which the most recently commissioned ship in a given context was officially placed into active service.
-
B.
firstCommissioned
Indicates that one entity was the first to formally authorize, request, or initiate the creation or execution of another entity.
-
C.
shipCommissionedDate
Indicates the date on which a ship was officially commissioned into service.
-
D.
recommissionedAsCarrierYear
Indicates the year in which an entity was recommissioned specifically in the role or configuration of a carrier.
-
E.
commissionedYear
Indicates the year in which something (typically a work, project, or item) was formally ordered, authorized, or put into production.
- 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.