Triple
T37880481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 世阿弥 元清 |
E944851
|
entity |
| Predicate | 代表的な業績 |
P181932
|
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.
功績の対象
Indicates a relationship where something is the object or target upon which a merit, achievement, or credit is based or directed.
-
B.
業績の影響
Indicates that one entity’s performance or results have an effect on, or bring about changes in, another entity or outcome.
-
C.
notableWorkPerformed
Indicates that an entity has created, executed, or contributed significantly to a particular work that is recognized as notable or important.
-
D.
主要業績
chosen
Indicates that something represents the primary achievements, accomplishments, or main performance outcomes associated with an entity.
-
E.
notableDeed
Indicates that an entity is recognized for performing a significant or noteworthy action or achievement.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.