Triple
T37339298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese aircraft carrier Chiyoda |
E926986
|
entity |
| Predicate | convertedToCarrier |
P141361
|
FINISHED |
| Object | 1943 |
—
|
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: 1943 | Statement: [Japanese aircraft carrier Chiyoda, convertedToCarrier, 1943]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedToCarrier Context triple: [Japanese aircraft carrier Chiyoda, convertedToCarrier, 1943]
-
A.
convertedBy
Indicates that one entity has been transformed or changed in form, state, or representation through the action or process performed by another entity.
-
B.
hasConvertedTo
chosen
Indicates that an entity has changed its previous state, status, form, or affiliation into a new one.
-
C.
convertedToSupport
Indicates that one entity has changed its stance, role, or configuration so that it now supports or aligns with another entity or cause.
-
D.
convertedIn
Indicates that one entity has been transformed, changed, or translated into another form, state, or representation within a specified context.
-
E.
convertedFrom
Indicates that one entity has been transformed or changed in form, type, or representation from 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.