Triple
T27931066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Home Fleet (Imperial German Navy) |
E707981
|
entity |
| Predicate | typeOfWarshipConcentrated |
P97528
|
FINISHED |
| Object | capital ships |
—
|
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: capital ships | Statement: [Home Fleet (Imperial German Navy), typeOfWarshipConcentrated, capital ships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfWarshipConcentrated Context triple: [Home Fleet (Imperial German Navy), typeOfWarshipConcentrated, capital ships]
-
A.
warshipTypeUsed
chosen
Indicates that a particular type or class of warship is employed or utilized in a given context, event, or operation.
-
B.
isWarshipOf
Indicates that a given warship belongs to, is operated by, or is part of the naval forces of a specified country or organization.
-
C.
isCapitalShip
Indicates that the subject vessel is classified as a capital ship, i.e., a primary, large, and heavily armed warship within a fleet.
-
D.
plannedArmamentClass
Indicates that an entity is intended or designated to be equipped with a particular class or type of armament.
-
E.
navalTechnologyType
Indicates the specific category or type of naval technology associated with an 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: April 27, 2026, 7:03 p.m.