Triple
T4382983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Force Outstanding Unit Award with Valor device |
E99171
|
entity |
| Predicate | deviceMaterial |
P618
|
FINISHED |
| Object | bronze |
—
|
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 | Statement: [Air Force Outstanding Unit Award with Valor device, deviceMaterial, bronze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deviceMaterial Context triple: [Air Force Outstanding Unit Award with Valor device, deviceMaterial, bronze]
-
A.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
B.
material
chosen
Indicates that one entity is physically composed of, made from, or constructed using the substance or material represented by the other entity.
-
C.
materialDepicted
Indicates that a work or representation visually portrays or includes a particular material as part of its subject.
-
D.
featuresMaterialFrom
Indicates that one entity incorporates, contains, or is composed of material originating from another entity.
-
E.
chassisMaterialFeature
Indicates that an entity has a chassis characterized by a specific material-related feature or property.
- 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.