Triple
T22564075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USNS Maury (T-AGS-16) |
E557895
|
entity |
| Predicate | acquiredByUSN |
P27319
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [USNS Maury (T-AGS-16), acquiredByUSN, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquiredByUSN Context triple: [USNS Maury (T-AGS-16), acquiredByUSN, 2014]
-
A.
acquiredByUSNavy
chosen
Indicates that something was obtained or taken into possession by the United States Navy.
-
B.
wasAcquiredByUSAThrough
Indicates that something came under the ownership, control, or sovereignty of the USA by means of a specified acquisition process or event.
-
C.
acquiredByNOAA
Indicates that something (such as data, imagery, or an asset) has been obtained or collected by the National Oceanic and Atmospheric Administration (NOAA).
-
D.
acquiredAsTrainingShip
Indicates that one entity obtained another specifically for use as a training ship.
-
E.
USNDesignation
Indicates the formal designation assigned by the United States Navy to identify and classify a ship, aircraft, or other naval asset.
- 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_69e11e5ae4ac8190b1f503457603d969 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15fa8d8388190856198547d56dce6 |
completed | April 29, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:52 p.m.