Triple
T28887234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Essex-class aircraft carriers |
E732598
|
entity |
| Predicate | lastActiveShip |
P36732
|
FINISHED |
| Object | USS Lexington (CV-16) |
—
|
NE NERFINISHED |
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: USS Lexington (CV-16) | Statement: [Essex-class aircraft carriers, lastActiveShip, USS Lexington (CV-16)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastActiveShip Context triple: [Essex-class aircraft carriers, lastActiveShip, USS Lexington (CV-16)]
-
A.
lastShip
chosen
Indicates that one entity is the final or most recent ship associated with another entity in a given sequence, context, or process.
-
B.
lastShipCommissioningDate
Indicates the date on which the most recently commissioned ship in a given context was officially placed into active service.
-
C.
lastVoyageYear
Indicates the calendar year in which an entity’s most recent voyage or journey took place.
-
D.
statusOfLeadShip
Indicates the current condition or state assigned to the primary or leading ship in a given context or operation.
-
E.
firstShip
Indicates that the subject is the earliest or initial ship associated with, created by, or used in relation to the object.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a72a4d08190a45476cd7a50a7cc |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:51 a.m.