Triple
T27155667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Order of Victoria and Albert |
E682511
|
entity |
| Predicate | insigniaAttachment |
P71862
|
FINISHED |
| Object | bow ribbon |
—
|
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: bow ribbon | Statement: [Royal Order of Victoria and Albert, insigniaAttachment, bow ribbon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: insigniaAttachment Context triple: [Royal Order of Victoria and Albert, insigniaAttachment, bow ribbon]
-
A.
insigniaSuspension
chosen
Indicates the method or manner in which an insignia is attached, hung, or suspended from a support or mounting.
-
B.
hasInsigniaComponent
Indicates that an entity includes, bears, or is composed of a particular insignia or emblem as one of its components.
-
C.
weaponMount
Indicates that one entity serves as a mounting point or support structure for attaching or holding a weapon on another entity.
-
D.
weaponFeature
Indicates that one entity is a characteristic, attribute, or functional aspect of a weapon.
-
E.
missionEquipment
Indicates that certain equipment is assigned to, used for, or associated with carrying out a specific mission.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f625069a00819096cf4b71a69a3563 |
completed | May 2, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 9:16 a.m.