Triple
T512890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Pennsylvania (BB-38) |
E10644
|
entity |
| Predicate | sunkAsTargetDate |
P3147
|
FINISHED |
| Object | 1948-02-10 |
—
|
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: 1948-02-10 | Statement: [USS Pennsylvania (BB-38), sunkAsTargetDate, 1948-02-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sunkAsTargetDate Context triple: [USS Pennsylvania (BB-38), sunkAsTargetDate, 1948-02-10]
-
A.
dateOfSinking
chosen
Indicates the specific calendar date on which an entity (typically a vessel or structure) sank.
-
B.
sunkBy
Indicates that one entity (typically a vessel or structure) was caused to sink or be destroyed in water by another entity.
-
C.
yearOfSinking
Indicates the specific calendar year in which an entity (typically a vessel or structure) sank.
-
D.
surrenderDate
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
-
E.
dateDestroyed
Indicates the specific date on which an entity was destroyed or ceased to exist.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f232fa688190b08a2fe3f22c7a6e |
completed | Feb. 28, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69a2f013c05481909e6dc87e7b20ebd8 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.