Triple
T19715401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ine Kusumoto |
E473462
|
entity |
| Predicate | typeOfPioneer |
P2809
|
FINISHED |
| Object | female medical pioneer in Japan |
—
|
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: female medical pioneer in Japan | Statement: [Ine Kusumoto, typeOfPioneer, female medical pioneer in Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPioneer Context triple: [Ine Kusumoto, typeOfPioneer, female medical pioneer in Japan]
-
A.
pioneerOf
chosen
Indicates that an entity was among the first to develop, introduce, or significantly advance another entity, concept, or practice.
-
B.
earlyExplorer
Indicates that an entity explored or investigated a place, field, or subject significantly earlier than most others.
-
C.
pioneeringAspect
Indicates that something embodies an innovative, trailblazing, or first-of-its-kind quality within a particular domain or context.
-
D.
visionaryOf
Indicates that one entity is the original conceiver or driving visionary behind the creation, direction, or concept of another entity.
-
E.
typeOfScientist
Indicates that one entity is a scientist and the other specifies the kind or specialization of that scientist.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6440cb47c81908124dfbd6f781d23 |
completed | April 20, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.