Triple
T20758564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Lionfish (SS-298) |
E510910
|
entity |
| Predicate | hasMastheadInsignia |
P133746
|
FINISHED |
| Object | lionfish emblem |
—
|
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: lionfish emblem | Statement: [USS Lionfish (SS-298), hasMastheadInsignia, lionfish emblem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMastheadInsignia Context triple: [USS Lionfish (SS-298), hasMastheadInsignia, lionfish emblem]
-
A.
hasInsigniaComponent
Indicates that an entity includes, bears, or is composed of a particular insignia or emblem as one of its components.
-
B.
hasMastheadFeature
Indicates that one entity is highlighted or featured in the masthead section of another entity (such as a page, site, or publication).
-
C.
hasTypeOfInsignia
Indicates that an entity bears or is associated with a specific kind or category of insignia.
-
D.
hasDistinctiveEmblem
chosen
Indicates that an entity possesses a unique symbol, logo, or emblem that serves to distinguish it from others.
-
E.
hasInescutcheon
Indicates that one heraldic shield or coat of arms bears another smaller shield (an inescutcheon) placed upon it.
- 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2464fb08190b6b141ca12d9f3f4 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:35 p.m.