Triple
T35965778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Chester (CA-27) |
E1040137
|
entity |
| Predicate | dateDamaged |
P13733
|
FINISHED |
| Object | 1942-10-20 |
—
|
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: 1942-10-20 | Statement: [USS Chester (CA-27), dateDamaged, 1942-10-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateDamaged Context triple: [USS Chester (CA-27), dateDamaged, 1942-10-20]
-
A.
dateOfLoss
chosen
Indicates the specific date on which a loss event (such as damage, theft, or other covered incident) occurred.
-
B.
repairDate
Indicates the date on which a repair action was performed or is scheduled to be performed on an entity.
-
C.
dateDestroyed
Indicates the specific date on which an entity was destroyed or ceased to exist.
-
D.
ruptureDate
Indicates the date on which a rupture event (such as a break, burst, or failure) occurs in the relationship between entities.
-
E.
decayDate
Indicates the date on which something ceases to be valid, effective, or usable (i.e., when it expires or decays).
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:07 p.m.