Triple
T8405367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Essex |
E198482
|
entity |
| Predicate | modernizedAs |
P32856
|
FINISHED |
| Object | attack aircraft carrier (CVA-9) |
—
|
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: attack aircraft carrier (CVA-9) | Statement: [USS Essex, modernizedAs, attack aircraft carrier (CVA-9)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernizedAs Context triple: [USS Essex, modernizedAs, attack aircraft carrier (CVA-9)]
-
A.
modernizedFor
chosen
Indicates that something has been updated, adapted, or improved to suit more recent standards, technologies, or conditions.
-
B.
modernizedBy
Indicates that an entity has been updated, improved, or brought up to modern standards through the actions or influence of another entity.
-
C.
modernizationType
Indicates the specific kind or category of modernization applied to an entity or system.
-
D.
modernization
Indicates a process by which something is updated, reformed, or transformed to align with contemporary standards, technologies, or practices.
-
E.
modernUse
Indicates how something is currently used or applied in modern times.
- 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_69ca8310df9c8190b25f16161cca3e41 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb8312941c8190af0b2def0a4e02be |
completed | March 31, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:05 p.m.