Triple
T33857579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle Fleet |
E867828
|
entity |
| Predicate | typeOfShipEmphasis |
P164057
|
FINISHED |
| Object | battleship-centric force |
—
|
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: battleship-centric force | Statement: [Battle Fleet, typeOfShipEmphasis, battleship-centric force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfShipEmphasis Context triple: [Battle Fleet, typeOfShipEmphasis, battleship-centric force]
-
A.
shipTypeFavored
chosen
Indicates that a particular type of ship is preferred or favored over others in a given context.
-
B.
shipClass
Indicates the classification or type category to which a particular ship belongs.
-
C.
originalShipType
Indicates the type or category of ship that an entity was originally classified or built as.
-
D.
isCapitalShip
Indicates that the subject vessel is classified as a capital ship, i.e., a primary, large, and heavily armed warship within a fleet.
-
E.
hasShipTypeCharacteristic
Indicates that a ship possesses a specific characteristic or property related to its type.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00d76d0e0881908d83a8dcce511167 |
completed | May 10, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_6a00d711805881909a94cfd1f25fb331 |
completed | May 10, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:47 a.m.