Triple
T689913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Distinguished Service Order |
E13368
|
entity |
| Predicate | ribbonPattern |
P9273
|
FINISHED |
| Object | red ribbon with narrow blue edges |
—
|
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: red ribbon with narrow blue edges | Statement: [Distinguished Service Order, ribbonPattern, red ribbon with narrow blue edges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ribbonPattern Context triple: [Distinguished Service Order, ribbonPattern, red ribbon with narrow blue edges]
-
A.
ribbonAdditionalStripes
Indicates that additional stripes are present on a ribbon beyond its primary or standard design.
-
B.
ribbonHasStripe
chosen
Indicates that a ribbon features one or more stripes as part of its pattern or design.
-
C.
kitPattern
Indicates the design or visual pattern featured on a team's kit or uniform.
-
D.
pattern
Indicates that one entity exhibits, follows, or is characterized by a particular recurring form, structure, or arrangement associated with another entity.
-
E.
camouflagePattern
Indicates that one entity has a surface or visual design intended to conceal it by blending with its surroundings or disrupting its outline.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0ad379c81909003d35c63822780 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d221d38819083c0adda81f59b07 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.