Triple
T34155539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoshino-class cruiser |
E876125
|
entity |
| Predicate | navalTechnologyType |
P178447
|
FINISHED |
| Object | protected cruiser |
—
|
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: protected cruiser | Statement: [Yoshino-class cruiser, navalTechnologyType, protected cruiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalTechnologyType Context triple: [Yoshino-class cruiser, navalTechnologyType, protected cruiser]
-
A.
navalTechnologyLevel
Indicates the relative advancement or sophistication of a party’s naval capabilities or maritime military technology.
-
B.
navalFeatures
Indicates that something possesses characteristics, components, or attributes specifically associated with naval or maritime contexts.
-
C.
navalPowerType
Indicates the classification of a naval force or capability according to its type or role within maritime power structures.
-
D.
navalTechnologySignificance
Indicates the importance or impact that a particular naval technology has within a given historical, strategic, or operational context.
-
E.
navalStandardType
Indicates the specific naval standard or classification system under which an entity (such as a vessel, equipment, or procedure) is defined or regulated.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7107acf0481909b01467b9ebbde01 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fb41a9c8190a121e62e510dc18a |
completed | May 3, 2026, 9:04 a.m. |
Created at: May 1, 2026, 1:54 a.m.