Triple
T35735008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love bracelet |
E1032862
|
entity |
| Predicate | hasEngravingOption |
P194723
|
FINISHED |
| Object | personalized engraving available |
—
|
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: personalized engraving available | Statement: [Love bracelet, hasEngravingOption, personalized engraving available]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEngravingOption Context triple: [Love bracelet, hasEngravingOption, personalized engraving available]
-
A.
hasEngravableArea
Indicates that an object possesses a surface or region suitable for being engraved.
-
B.
hasImprintStyle
Indicates that one entity bears or exhibits a particular style, pattern, or form of imprint associated with another entity.
-
C.
hasSubImprintFeature
Indicates that an imprint includes or is associated with a more specific subordinate imprint feature.
-
D.
hasWinnerEngraved
Indicates that the winner of a competition, event, or award is permanently recorded or inscribed on an associated object or medium.
-
E.
hasCarving
Indicates that one entity features or contains a carved design, inscription, or sculpted detail that is associated with or applied to another entity.
- 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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
| PDg | Predicate description generation | batch_69fd82ebe1c081908455fc45b6e45178 |
completed | May 8, 2026, 6:30 a.m. |
Created at: May 3, 2026, 4:05 p.m.