Triple
T35804175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 金鯱 |
E1035061
|
entity |
| Predicate | デザイン要素 |
P95346
|
FINISHED |
| Object | 尾が大きく反り返る意匠を持つ |
—
|
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: 尾が大きく反り返る意匠を持つ | Statement: [金鯱, デザイン要素, 尾が大きく反り返る意匠を持つ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: デザイン要素 Context triple: [金鯱, デザイン要素, 尾が大きく反り返る意匠を持つ]
-
A.
designAspect
Indicates that one entity represents a particular design-related feature, characteristic, or consideration of another entity.
-
B.
typicalDesignElement
chosen
Indicates that something is a common or characteristic design feature typically found in or associated with another entity.
-
C.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
D.
visualElements
Indicates that one entity contains, uses, or is characterized by specific visual components or graphical features associated with another entity.
-
E.
designBureau
Indicates that an entity functions as a design bureau responsible for planning, developing, or engineering designs for another entity or project.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.