Triple
T31161974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Đông Hồ painting village |
E794364
|
entity |
| Predicate | usesColorSource |
P191362
|
FINISHED |
| Object | charred bamboo leaves |
—
|
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: charred bamboo leaves | Statement: [Đông Hồ painting village, usesColorSource, charred bamboo leaves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesColorSource Context triple: [Đông Hồ painting village, usesColorSource, charred bamboo leaves]
-
A.
colorUse
Indicates that one entity uses, applies, or is associated with a particular color in its appearance, design, or representation.
-
B.
hasColorReference
Indicates that one entity serves as a reference or source for determining or specifying the color associated with another entity.
-
C.
isColor
Indicates that one entity represents the color attribute or hue of another entity.
-
D.
coversColorSpace
Indicates that one entity’s color representation range fully includes or spans the color space defined by another entity.
-
E.
usesColorMatchingFunctions
Indicates that one entity applies color matching functions to relate or convert color stimuli between different color spaces or representations.
- 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_69f224d504908190b01278dcb7fc3fa7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: April 29, 2026, 9:07 p.m.