Triple
T11741805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 桂川 |
E279172
|
entity |
| Predicate | 文化的意義 |
P1579
|
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.
isCulturalSignificance
Indicates that something holds notable meaning, value, or influence within a particular culture or cultural context.
-
B.
hasCulturalSignificance
chosen
Indicates that something holds notable meaning, value, or importance within a particular culture or cultural context.
-
C.
culturalKnowledge
Indicates that one entity possesses or conveys understanding of the customs, practices, values, or traditions associated with a particular culture.
-
D.
hasCulturalInterpretation
Indicates that something is understood, represented, or given meaning within a particular cultural context or tradition.
-
E.
culturalCategory
Indicates that one entity classifies or groups another entity according to a particular culture, tradition, or culturally defined type.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4f191388190bd6ef7e80c41ca48 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.