Triple
T4997011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wound Badge in Gold |
E112271
|
entity |
| Predicate | decorativeFinish |
P61388
|
FINISHED |
| Object | gold-colored finish |
—
|
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: gold-colored finish | Statement: [Wound Badge in Gold, decorativeFinish, gold-colored finish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decorativeFinish Context triple: [Wound Badge in Gold, decorativeFinish, gold-colored finish]
-
A.
typicalFinish
Indicates that an action, process, or event commonly or characteristically ends with a particular outcome or state.
-
B.
decoration
Indicates that one entity serves as an ornament or embellishing element for another entity, enhancing its appearance or style.
-
C.
decorations
Indicates that one entity adds, provides, or serves as ornamental or decorative elements for another entity.
-
D.
adornedWith
Indicates that one entity is decorated, embellished, or ornamented by another entity.
-
E.
decorationCompletedUnder
Indicates that the completion of a decoration activity occurred under the responsibility, authority, or conditions associated with a specified entity or context.
- 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_69bd4432b32c81909f3b3c6bd10f0653 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7472a1dc8190942f568a81fdd961 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd714aee2481908fb0dd5fa2daf3a1 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd74713fc88190916c2b04cd2e677e |
completed | March 20, 2026, 4:23 p.m. |
Created at: March 20, 2026, 1:34 p.m.