Triple
T3613392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ORP Błyskawica |
E76540
|
entity |
| Predicate | memorialFunction |
P500
|
FINISHED |
| Object | commemorates Polish Navy sailors of World War II |
—
|
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: commemorates Polish Navy sailors of World War II | Statement: [ORP Błyskawica, memorialFunction, commemorates Polish Navy sailors of World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memorialFunction Context triple: [ORP Błyskawica, memorialFunction, commemorates Polish Navy sailors of World War II]
-
A.
hasMemorial
Indicates that a memorial exists in honor of, or dedicated to, a particular entity.
-
B.
memorialization
Indicates the act of preserving the memory or honoring the legacy of someone or something, often through a dedicated object, event, or practice.
-
C.
memorialType
Indicates the specific kind or category of memorial associated with an entity (e.g., plaque, statue, monument).
-
D.
memorialName
Indicates that a memorial is known by or designated with a particular name.
-
E.
commemoratedBy
chosen
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2786f808190be4e42734a79d74e |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83d8b1c8190b3bddbc5dc995a87 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.