Triple
T221663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BB-39 |
E4226
|
entity |
| Predicate | decommissionedReason |
P10134
|
FINISHED |
| Object | sunk in combat |
—
|
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: sunk in combat | Statement: [BB-39, decommissionedReason, sunk in combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decommissionedReason Context triple: [BB-39, decommissionedReason, sunk in combat]
-
A.
discontinuedIn
Indicates that an item, product, or service stopped being produced, offered, or supported starting in a specified time or place.
-
B.
dissolvedOrAbolished
Indicates that an organization, institution, or formal entity has been officially terminated, disbanded, or ceased to exist.
-
C.
replacedSystemUsedUntil
Indicates that one system was used up until it was replaced by another system.
-
D.
dateAbolished
Indicates the date on which something (such as an institution, law, practice, or position) was officially ended or abolished.
-
E.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25efd0df48190b8fef4c422a1265f |
completed | Feb. 28, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69a25b54d790819093b35bd1a6f00f92 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25efc13308190900a86ca0367c9b3 |
completed | Feb. 28, 2026, 3:20 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.