Triple
T4267006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kongō-class battlecruiser |
E96848
|
entity |
| Predicate | laterReclassifiedAs |
P22031
|
FINISHED |
| Object | fast battleship |
—
|
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: fast battleship | Statement: [Kongō-class battlecruiser, laterReclassifiedAs, fast battleship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterReclassifiedAs Context triple: [Kongō-class battlecruiser, laterReclassifiedAs, fast battleship]
-
A.
reclassifiedAs
chosen
Indicates that an entity’s classification or category has been changed from a previous one to a new one.
-
B.
reclassifiedBy
Indicates that an entity’s classification or category has been changed by a specific agent or authority.
-
C.
laterReinterpretedAs
Indicates that something was originally understood or classified one way but was subsequently given a different interpretation or meaning at a later time.
-
D.
laterDescribedAs
Indicates that an entity is referred to or characterized by a particular description or label at a later time.
-
E.
laterRepurposedFor
Indicates that something was originally used for one purpose and subsequently assigned a different, new purpose.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34fce710481909d90ed4a3d150fde |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.