Triple
T8606164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portsmouth Naval Memorial |
E203801
|
entity |
| Predicate | hasRollOfHonour |
P83828
|
FINISHED |
| Object | Royal Navy casualties |
—
|
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 casualties | Statement: [Portsmouth Naval Memorial, hasRollOfHonour, Royal Navy casualties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRollOfHonour Context triple: [Portsmouth Naval Memorial, hasRollOfHonour, Royal Navy casualties]
-
A.
hasVictoriaCrossRecipient
Indicates that an entity has, is associated with, or includes at least one recipient of the Victoria Cross.
-
B.
majorHonourCount
Indicates the number of significant or top-level honors or awards associated with an entity.
-
C.
hasNotableHonor
Indicates that an entity has received a significant award, title, or formal recognition of distinction.
-
D.
honoursAsPlayer
Indicates that one entity has received awards, recognitions, or honours specifically for their role or achievements as a player.
-
E.
isGallantryAward
Indicates that the subject is a formal gallantry award, i.e., an honor conferred in recognition of exceptional bravery or valor.
- F. None of above. chosen
Provenance (4 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46e9b6a881908f6a6c847519e5e5 |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:25 p.m.