Triple
T16229847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RVN Gallantry Cross with Palm |
E393949
|
entity |
| Predicate | deviceRepresents |
P122246
|
FINISHED |
| Object | citation at Armed Forces level |
—
|
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: citation at Armed Forces level | Statement: [RVN Gallantry Cross with Palm, deviceRepresents, citation at Armed Forces level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deviceRepresents Context triple: [RVN Gallantry Cross with Palm, deviceRepresents, citation at Armed Forces level]
-
A.
deviceIndicates
Indicates that a device provides a signal, status, or output that conveys information about a condition, event, or state.
-
B.
portraysDevice
Indicates that one entity visually represents or depicts a device in some medium or context.
-
C.
valorDeviceIndicates
Indicates that a Valor device is signaling, reporting, or otherwise providing evidence of a particular state, condition, or event.
-
D.
componentRepresents
Indicates that one component stands in for, symbolizes, or models another entity or concept within a system or context.
-
E.
deviceModel
Indicates the specific model designation associated with a device.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d29438c81909aa2724cc47bb959 |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:03 a.m.