Triple
T23318967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USNS Littlehales (T-AGS-52) |
E590793
|
entity |
| Predicate | conversionCompletedAsNOAAShip |
P6312
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [USNS Littlehales (T-AGS-52), conversionCompletedAsNOAAShip, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionCompletedAsNOAAShip Context triple: [USNS Littlehales (T-AGS-52), conversionCompletedAsNOAAShip, 2003]
-
A.
conversionCompleted
chosen
Indicates that a previously initiated conversion process has finished successfully.
-
B.
conversionOfShip
Indicates the process by which a ship is altered or transformed from one configuration, role, or specification into another.
-
C.
shipCompleted
Indicates that a shipping process or delivery has been fully completed for the associated item or order.
-
D.
conversionStatus
Indicates the current state or outcome of a process in which one entity is transformed, converted, or transitioned into another form or status.
-
E.
shipCommissionedAs
Indicates that a ship entered active service under a specific name or designation at the time of its commissioning.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1978372948190bad066893c4e0768 |
completed | April 29, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:07 p.m.