Triple
T30785948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 国立文楽劇場 |
E783954
|
entity |
| Predicate | 国際的文脈 |
P1499
|
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.
internationalIntegration
Indicates the extent to which entities are connected, coordinated, or unified across national boundaries within shared systems, processes, or structures.
-
B.
国際分類
Indicates a relationship where something is assigned or referred to by an international classification system.
-
C.
isInternational
chosen
Indicates that something has a connection to, involves, or extends across more than one country.
-
D.
internationalConcern
Indicates that an issue, event, or situation is regarded as significant or problematic by multiple countries or the international community as a whole.
-
E.
internationalContribution
Indicates that an entity provides resources, support, or participation that benefits or advances activities beyond its own country at an international level.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f690097c9c81909858e7d8c15474da |
completed | May 3, 2026, midnight |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:41 p.m.