Triple
T24695452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Furutaka |
E611570
|
entity |
| Predicate | reconstructionDetails |
P156997
|
FINISHED |
| Object | torpedo armament upgraded |
—
|
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: torpedo armament upgraded | Statement: [Furutaka, reconstructionDetails, torpedo armament upgraded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reconstructionDetails Context triple: [Furutaka, reconstructionDetails, torpedo armament upgraded]
-
A.
reconstructionDetails
chosen
Indicates that there is information specifying how something was rebuilt, restored, or reassembled after damage, loss, or alteration.
-
B.
reconstructionWork
Indicates that an entity is engaged in or associated with activities to rebuild, restore, or repair something that was damaged, destroyed, or altered.
-
C.
reconstructionFor
Indicates that one entity serves as a reconstruction, restoration, or rebuilt version of another entity.
-
D.
reconstructionBuilt
Indicates that one entity carried out or was responsible for constructing a rebuilt or restored version of another entity.
-
E.
reconstructionFeature
Indicates that one entity serves as a feature, component, or characteristic used in the reconstruction or restoration of another entity.
- 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 3:21 a.m.