Triple
T22254666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rorke's Drift mission station |
E550066
|
entity |
| Predicate | numberOfVictoriaCrossesAwarded |
P147568
|
FINISHED |
| Object | 11 |
—
|
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: 11 | Statement: [Rorke's Drift mission station, numberOfVictoriaCrossesAwarded, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfVictoriaCrossesAwarded Context triple: [Rorke's Drift mission station, numberOfVictoriaCrossesAwarded, 11]
-
A.
hasVictoriaCrossRecipient
Indicates that an entity has, is associated with, or includes at least one recipient of the Victoria Cross.
-
B.
numberOfNavyCrosses
Indicates the quantity of Navy Cross military decorations associated with an entity.
-
C.
dateOfActionForVictoriaCross
Indicates the specific date on which the action occurred for which the Victoria Cross was awarded.
-
D.
battleHonoursCount
Indicates the number of battle honours associated with an entity, such as a military unit, ship, or individual.
-
E.
victoriaCrossActionDate
Indicates the date on which the action or deed occurred that led to the awarding of the Victoria Cross.
- 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f138c1d70881908df47b0f818c0022 |
completed | April 28, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:39 p.m.