Triple
T35380760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yumi Yoshimura |
E1022637
|
entity |
| Predicate | sharesVocalDutiesWith |
P26607
|
FINISHED |
| Object | Ami Onuki |
—
|
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: Ami Onuki | Statement: [Yumi Yoshimura, sharesVocalDutiesWith, Ami Onuki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesVocalDutiesWith Context triple: [Yumi Yoshimura, sharesVocalDutiesWith, Ami Onuki]
-
A.
hasResponsibilitiesSharedWith
Indicates that two or more entities share joint responsibility for certain tasks, duties, or obligations.
-
B.
sharesWorkWith
chosen
Indicates that one entity collaborates or participates jointly in work or tasks with another entity.
-
C.
sharesPowerWith
Indicates that two or more entities jointly hold, exercise, or distribute authority or control in a shared manner.
-
D.
sharesChorusWith
Indicates that two musical works have the same or substantially similar chorus section.
-
E.
sharesRoleWith
Indicates that two entities hold the same role or position within a given context or system.
- 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a005e8a2f7c819085bfc6f04b866d87 |
completed | May 10, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_6a005de82ef08190a015b385d1d3443c |
completed | May 10, 2026, 10:28 a.m. |
Created at: May 3, 2026, 4:03 p.m.