Triple
T26235948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commendation for Gallantry |
E656165
|
entity |
| Predicate | gradeInSystem |
P160385
|
FINISHED |
| Object | fourth level award |
—
|
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: fourth level award | Statement: [Commendation for Gallantry, gradeInSystem, fourth level award]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gradeInSystem Context triple: [Commendation for Gallantry, gradeInSystem, fourth level award]
-
A.
gradeInSystem
chosen
Indicates that a particular grade or evaluation result is recorded and stored within a specific grading or information system.
-
B.
gradingSystem
Indicates the method or criteria by which performance, quality, or achievement is evaluated and assigned a grade or score.
-
C.
gradeIn
Indicates that an entity has a particular grade or score within a specified course, assignment, or evaluation context.
-
D.
gradeNumber
Indicates the numerical grade or level assigned to an entity within an ordered grading or classification system.
-
E.
gradeCategory
Indicates the classification of a grade into a broader category or level (such as letter grade, performance band, or pass/fail group).
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 9:01 p.m.