Triple
T30399378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Yao |
E773307
|
entity |
| Predicate | traditionalJewelryMaterial |
P50559
|
FINISHED |
| Object | silver |
—
|
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: silver | Statement: [Red Yao, traditionalJewelryMaterial, silver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalJewelryMaterial Context triple: [Red Yao, traditionalJewelryMaterial, silver]
-
A.
associatedMetal
Indicates a relationship where one entity is linked or connected to a particular metal, such as by composition, usage, origin, or symbolic association.
-
B.
typeOfJewellery
Indicates the specific kind or category of jewellery that an item belongs to.
-
C.
preciousStones
Indicates that one entity possesses or is associated with stones that are considered valuable or precious.
-
D.
typicalJewellery
Indicates that the object is a kind of jewellery that is commonly or characteristically associated with the given entity.
-
E.
traditionalMaterial
chosen
Indicates that something is made from, incorporates, or is characterized by materials associated with long-established or customary practices.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: April 29, 2026, 8:03 p.m.