Triple
T16896134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese destroyer Yukikaze |
E424303
|
entity |
| Predicate | preservedPart |
P124914
|
FINISHED |
| Object | rudder |
—
|
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: rudder | Statement: [Japanese destroyer Yukikaze, preservedPart, rudder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preservedPart Context triple: [Japanese destroyer Yukikaze, preservedPart, rudder]
-
A.
partlyPreservedAs
Indicates that an entity is only partially preserved or remains in incomplete form within another entity or context.
-
B.
partiallyPreserved
Indicates that the referenced entity or object is only incompletely intact, with some parts missing, damaged, or lost while others remain.
-
C.
partiallyPreservedThrough
Indicates that something is not fully intact but has been maintained or conserved to some extent by or via another entity or medium.
-
D.
somePreservedAs
Indicates that at least one part or instance of an entity is kept or maintained in a particular state, form, or condition.
-
E.
isPreservedBy
Indicates that something remains unchanged, intact, or maintained as it is due to the action or influence of a particular agent or process.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8d880208190ad2b2c8616b54ea3 |
completed | April 18, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e32e2c07b081908c8fee9f5507bb9e |
completed | April 18, 2026, 7:09 a.m. |
Created at: April 10, 2026, 5:29 a.m.