Triple
T4382970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Force Outstanding Unit Award with Valor device |
E99171
|
entity |
| Predicate | denotedBy |
P54139
|
FINISHED |
| Object | bronze V device |
—
|
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: bronze V device | Statement: [Air Force Outstanding Unit Award with Valor device, denotedBy, bronze V device]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotedBy Context triple: [Air Force Outstanding Unit Award with Valor device, denotedBy, bronze V device]
-
A.
designationFor
Indicates that one entity serves as the official title, label, or role name assigned to another entity.
-
B.
areRepresentedBy
chosen
Indicates that one entity serves as a representation, proxy, or stand-in for another entity.
-
C.
posedBy
Indicates that something (such as a question, problem, challenge, or threat) is presented, raised, or created by a particular entity.
-
D.
embodiedBy
Indicates that an abstract concept, role, or function is physically or concretely realized in a specific entity.
-
E.
namedIn
Indicates that one entity is explicitly mentioned or referenced by name within another entity (such as a document, statement, or record).
- 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_69b3454ea8f48190a49c2436624d6ef6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35262649c8190a724c9835cb7ece6 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:18 p.m.