Triple
T38262018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scharnhorst-class armored cruiser |
E1017951
|
entity |
| Predicate | navalTechnologyPeriod |
P42687
|
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: [Scharnhorst-class armored cruiser, navalTechnologyPeriod, pre-dreadnought era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalTechnologyPeriod Context triple: [Scharnhorst-class armored cruiser, navalTechnologyPeriod, pre-dreadnought era]
-
A.
navalEra
chosen
Indicates the historical period or era in which a naval-related event, activity, or condition takes place.
-
B.
navalTechnologySignificance
Indicates the importance or impact that a particular naval technology has within a given historical, strategic, or operational context.
-
C.
navalTechnologyLevel
Indicates the relative advancement or sophistication of a party’s naval capabilities or maritime military technology.
-
D.
navalTechnologyType
Indicates the specific category or type of naval technology associated with an entity.
-
E.
navalArmament
Indicates that one entity serves as the naval weaponry or sea-based military equipment of 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:30 p.m.