Triple
T3841719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikuma |
E93464
|
entity |
| Predicate | shipClassRole |
P3141
|
FINISHED |
| Object | fleet 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: fleet cruiser | Statement: [Mikuma, shipClassRole, fleet cruiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipClassRole Context triple: [Mikuma, shipClassRole, fleet cruiser]
-
A.
shipClass
chosen
Indicates the classification or type category to which a particular ship belongs.
-
B.
hasShipRole
Indicates that an entity holds or is assigned a specific role or function on a ship.
-
C.
tonnageClass
Indicates a classification relationship where an entity is assigned to a category based on its tonnage (weight or carrying capacity range).
-
D.
navalTacticRole
Indicates the specific tactical function or role an entity performs within a naval operation or maritime combat context.
-
E.
shipRepresents
Indicates that one entity (typically a ship) serves as a symbol, stand-in, or representation for another entity, concept, or group.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeebb235088190b115623e54ea2ab1 |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.