Triple
T28852361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RCOC cap badge |
E728634
|
entity |
| Predicate | partOfUniform |
P18730
|
FINISHED |
| Object | Royal Canadian Ordnance Corps dress uniform |
—
|
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: Royal Canadian Ordnance Corps dress uniform | Statement: [RCOC cap badge, partOfUniform, Royal Canadian Ordnance Corps dress uniform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfUniform Context triple: [RCOC cap badge, partOfUniform, Royal Canadian Ordnance Corps dress uniform]
-
A.
partOfStyle
Indicates that one style is a component, subset, or constituent element of another, more encompassing style.
-
B.
wearsOnUniform
chosen
Indicates that an item is part of and is worn as a component of a uniform.
-
C.
partOfFront
Indicates that one entity constitutes a component or section located at the front portion of another entity.
-
D.
shapePart
Indicates that one entity is a component or sub-part of the overall shape or geometric structure of another entity.
-
E.
coatCharacteristic
Indicates that one entity has a particular property, feature, or quality that characterizes its outer covering or surface.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: April 28, 2026, 6:44 a.m.