Triple
T38602751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CVS-14 |
E934257
|
entity |
| Predicate | associatedShipConversion |
P21289
|
FINISHED |
| Object | SCB modernization program |
—
|
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: SCB modernization program | Statement: [CVS-14, associatedShipConversion, SCB modernization program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedShipConversion Context triple: [CVS-14, associatedShipConversion, SCB modernization program]
-
A.
conversionOfShip
chosen
Indicates the process by which a ship is altered or transformed from one configuration, role, or specification into another.
-
B.
componentShip
Indicates that one entity is a physical or logical component or part of another entity, such that the whole is composed of or depends on that component.
-
C.
assistedShip
Indicates that one entity helped or supported a ship in performing an operation, task, or journey.
-
D.
usedForShips
Indicates that something is designed, intended, or suitable to be used for ships or ship-related purposes.
-
E.
boardsShip
Indicates that one entity gets onto or enters a ship as a passenger or crew member.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.