Triple
T22220608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Reserve Components Achievement Medal |
E549197
|
entity |
| Predicate | frontDesignFeature |
P45253
|
FINISHED |
| Object | Minuteman figure |
—
|
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: Minuteman figure | Statement: [Army Reserve Components Achievement Medal, frontDesignFeature, Minuteman figure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontDesignFeature Context triple: [Army Reserve Components Achievement Medal, frontDesignFeature, Minuteman figure]
-
A.
frontDesign
chosen
Indicates that one entity serves as the primary or visible front-facing design or appearance of another entity.
-
B.
frontType
Indicates the type or category of a front (e.g., boundary or leading side) that one entity presents or forms relative to another.
-
C.
frontMaterial
Indicates that one entity is the material that forms the front surface or front-facing part of another entity.
-
D.
previousDesignFeature
Indicates that one design feature precedes another in a sequence or earlier version of a design.
-
E.
designedFeature
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
- 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_69e11e403d6481909a94d0aaf157f6ef |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b8fa3d081908db0a0556b009d8f |
completed | April 28, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:37 p.m.