Triple
T14693907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Submarine Flotilla (SUBFLOT) |
E345103
|
entity |
| Predicate | emblemUser |
P29556
|
FINISHED |
| Object | Royal Navy Submarine Service insignia |
—
|
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: Royal Navy Submarine Service insignia | Statement: [Submarine Flotilla (SUBFLOT), emblemUser, Royal Navy Submarine Service insignia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emblemUser Context triple: [Submarine Flotilla (SUBFLOT), emblemUser, Royal Navy Submarine Service insignia]
-
A.
emblemName
Indicates that a specified name is the official or recognized title of an emblem.
-
B.
emblemStatus
Indicates the current state or condition of an emblem, such as whether it is active, valid, displayed, or in use.
-
C.
emblemUsedBy
chosen
Indicates that a particular emblem is adopted or employed by a specific entity as its symbol or identifying mark.
-
D.
emblemText
Indicates that a piece of text serves as the inscription or wording displayed on an emblem.
-
E.
emblemGlyph
Indicates that one entity serves as the specific glyph or graphic symbol used as the emblem for another 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb586e7108190be644db9cf9a4d99 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.