Triple
T26062547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nishijin district |
E657301
|
entity |
| Predicate | hasMaterialProduced |
P26032
|
FINISHED |
| Object | silk brocade |
—
|
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: silk brocade | Statement: [Nishijin district, hasMaterialProduced, silk brocade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaterialProduced Context triple: [Nishijin district, hasMaterialProduced, silk brocade]
-
A.
hasProduction
chosen
Indicates that an entity is associated with, or responsible for, the creation or manufacture of another entity or product.
-
B.
hasProductionStatus
Indicates the current stage or condition of an entity’s production process (e.g., planned, in progress, completed, or discontinued).
-
C.
hasProductionValue
Indicates that something possesses or is associated with a particular level or type of production quality or cost.
-
D.
hasProductionElements
Indicates that something includes or is associated with specific components, materials, or elements used in its production or creation.
-
E.
hasPrintedMaterials
Indicates that an entity possesses or is associated with physical printed materials (such as books, brochures, or documents).
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 26, 2026, 7:19 p.m.