Triple
T35334445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dokin-chan |
E1020413
|
entity |
| Predicate | sometimesCooperatesWith |
P39566
|
FINISHED |
| Object | Anpanman and friends |
—
|
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: Anpanman and friends | Statement: [Dokin-chan, sometimesCooperatesWith, Anpanman and friends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sometimesCooperatesWith Context triple: [Dokin-chan, sometimesCooperatesWith, Anpanman and friends]
-
A.
involvesCooperation
Indicates that the related entities participate together in a shared activity or goal that requires mutual assistance or coordinated effort.
-
B.
cooperateThrough
Indicates that entities work together or coordinate their actions by means of a specific intermediary, method, or channel.
-
C.
definesCooperationWith
Indicates that one entity formally specifies or establishes the terms, scope, or nature of cooperative interaction with another entity.
-
D.
hasCooperative
chosen
Indicates that one entity participates in a cooperative relationship or partnership with another entity.
-
E.
isCooperative
Indicates that an entity engages willingly and constructively in joint actions or relationships with others, working together toward shared goals.
- 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.