Triple
T33329551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 仁徳天皇 |
E853363
|
entity |
| Predicate | 伝承上の業績 |
P36130
|
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.
notableWorkPerformed
Indicates that an entity has created, executed, or contributed significantly to a particular work that is recognized as notable or important.
-
B.
notablePerformanceTradition
Indicates a recognized and enduring pattern or custom in how a performance is typically presented or carried out.
-
C.
notableDeed
chosen
Indicates that an entity is recognized for performing a significant or noteworthy action or achievement.
-
D.
notableWork
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by another entity.
-
E.
honoursLegacyOf
Indicates that one entity actively preserves, respects, or celebrates the memory, values, or achievements of another entity from the past.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.