Triple
T26045681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Wilmington (CL-79) |
E647820
|
entity |
| Predicate | shipRolePlanned |
P130419
|
FINISHED |
| Object | light cruiser |
—
|
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: light cruiser | Statement: [USS Wilmington (CL-79), shipRolePlanned, light cruiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipRolePlanned Context triple: [USS Wilmington (CL-79), shipRolePlanned, light cruiser]
-
A.
shipDraft
Indicates the depth of a ship’s hull below the waterline, typically representing how deeply the vessel sits in the water.
-
B.
shipAssignment
Indicates the association between a ship and the specific task, route, or entity it has been assigned to.
-
C.
shipFunction
chosen
Indicates that one entity serves as the functional role, purpose, or operational use of a ship.
-
D.
hasShipRole
Indicates that an entity holds or is assigned a specific role or function on a ship.
-
E.
shipUsed
Indicates that a particular ship was employed or utilized in carrying out an event, activity, or operation.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6065a844c81908e04d361469aa3c5 |
completed | May 2, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:10 a.m.