Triple
T15374087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chenghua doucai porcelain |
E367621
|
entity |
| Predicate | firingDetail |
P118500
|
FINISHED |
| Object | first firing for underglaze blue |
—
|
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: first firing for underglaze blue | Statement: [Chenghua doucai porcelain, firingDetail, first firing for underglaze blue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firingDetail Context triple: [Chenghua doucai porcelain, firingDetail, first firing for underglaze blue]
-
A.
firingCharacteristic
Indicates the specific way in which an entity initiates or sustains firing or discharge, such as its pattern, mode, or conditions of activation.
-
B.
firingPlatform
Indicates a platform or structure from which a weapon or projectile is launched or fired.
-
C.
firedBy
Indicates that one entity has dismissed or terminated another entity from a position, role, or employment.
-
D.
firedAt
Indicates that one entity discharged a weapon or projectile in the direction of another entity.
-
E.
firingControl
Indicates a relationship where one entity directs, regulates, or initiates the firing or discharge action of another entity or system.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e5d6f808190b0a4cdb35dc89e69 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:18 a.m.