Triple
T655002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokugawa shogunate navy |
E11628
|
entity |
| Predicate | modernizedIn |
P4337
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Tokugawa shogunate navy, modernizedIn, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernizedIn Context triple: [Tokugawa shogunate navy, modernizedIn, 19th century]
-
A.
modernizedBy
Indicates that an entity has been updated, improved, or brought up to modern standards through the actions or influence of another entity.
-
B.
modernization
chosen
Indicates a process by which something is updated, reformed, or transformed to align with contemporary standards, technologies, or practices.
-
C.
modernUse
Indicates how something is currently used or applied in modern times.
-
D.
modernizationFeatures
Indicates that something includes characteristics, elements, or improvements associated with making it more modern or up to date.
-
E.
modernPractice
Indicates that an entity engages in or reflects a contemporary, up-to-date way of doing something, following current methods, standards, or trends.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f4d57688190a9515ac494a97b22 |
completed | March 1, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69a49d121cec81909986c91291bb4ca8 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.