Triple
T24935571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raku ware |
E623300
|
entity |
| Predicate | hasNotableMaker |
P78804
|
FINISHED |
| Object | Raku Kichizaemon family |
—
|
NE NERFINISHED |
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: Raku Kichizaemon family | Statement: [Raku ware, hasNotableMaker, Raku Kichizaemon family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableMaker Context triple: [Raku ware, hasNotableMaker, Raku Kichizaemon family]
-
A.
hasNotableDeveloper
Indicates that an entity has a developer who is particularly prominent, influential, or otherwise notable.
-
B.
hasNotableContentCreator
Indicates that an entity is associated with a content creator who is recognized as notable or prominent.
-
C.
hasNotableExpositor
Indicates that an entity has a person or source that is especially recognized for explaining, interpreting, or presenting it.
-
D.
notableMaker
chosen
Indicates that one entity is a well-known or significant creator, producer, or manufacturer of the other entity.
-
E.
hasNotableComposer
Indicates that an entity is associated with a composer who is recognized as particularly significant or distinguished.
- 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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 18, 2026, 5:30 a.m.