Triple
T10424291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dingyuan |
E245743
|
entity |
| Predicate | navalTechnologyLevel |
P93514
|
FINISHED |
| Object | pre-dreadnought era |
—
|
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: pre-dreadnought era | Statement: [Dingyuan, navalTechnologyLevel, pre-dreadnought era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalTechnologyLevel Context triple: [Dingyuan, navalTechnologyLevel, pre-dreadnought era]
-
A.
navalTechnologySignificance
Indicates the importance or impact that a particular naval technology has within a given historical, strategic, or operational context.
-
B.
navalTechnologyImplication
Indicates that one naval technology leads to, enables, or logically implies the development, use, or effectiveness of another naval technology or capability.
-
C.
navalFeatures
Indicates that something possesses characteristics, components, or attributes specifically associated with naval or maritime contexts.
-
D.
hasNavalComponent
Indicates that something includes, involves, or is associated with a naval or maritime element as part of its composition or structure.
-
E.
navalPowerStatus
Indicates the relative strength, capability, or strategic standing of an entity’s naval forces compared to others or to defined benchmarks.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea47a6408190a87b32760692487f |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e91de3088190ae89cbb12fb29db8 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:12 p.m.