Triple
T3255928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roll of Honour |
E68294
|
entity |
| Predicate | hasTypeOfNames |
P46902
|
FINISHED |
| Object | killed in action |
—
|
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: killed in action | Statement: [Roll of Honour, hasTypeOfNames, killed in action]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfNames Context triple: [Roll of Honour, hasTypeOfNames, killed in action]
-
A.
hasTypeName
Indicates that an entity is associated with a specific type name used to classify or identify its kind.
-
B.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
hasTypeOfCase
Indicates that an entity is associated with or classified under a particular type or category of case.
-
D.
onNameTypeLists
Indicates that something appears on one or more lists that are categorized or organized by name type.
-
E.
hasMemberType
Indicates that an entity includes or is associated with members belonging to a specified type or category.
- 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf6753b0819081755a529fd87cb1 |
completed | March 8, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada525bb2c8190b773efe6d696b6ab |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:09 p.m.