Triple
T26259654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS New Haven (CL-76) |
E656811
|
entity |
| Predicate | neverCompletedAs |
P160174
|
FINISHED |
| Object | Cleveland-class light cruiser |
—
|
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: Cleveland-class light cruiser | Statement: [USS New Haven (CL-76), neverCompletedAs, Cleveland-class light cruiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neverCompletedAs Context triple: [USS New Haven (CL-76), neverCompletedAs, Cleveland-class light cruiser]
-
A.
hasNotCompleted
Indicates that an entity has an expected task, process, or requirement that remains unfinished or not yet fulfilled.
-
B.
neverPerformed
Indicates that the specified action or event has not occurred at any time for the given entity or between the given entities.
-
C.
unfinished
Indicates that an action, process, or state has started but has not yet been completed.
-
D.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
E.
neverLaunched
Indicates that an entity (such as a product, project, or mission) was planned or created but was never officially initiated, released, or put into operation.
- F. None of above. chosen
Provenance (4 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dfdd57c81908d069fc4b8124ff7 |
completed | May 2, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 26, 2026, 9:09 p.m.