Triple
T31960085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meiko Honma |
E816012
|
entity |
| Predicate | causeOfReunionOf |
P185662
|
FINISHED |
| Object | Super Peace Busters |
—
|
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: Super Peace Busters | Statement: [Meiko Honma, causeOfReunionOf, Super Peace Busters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfReunionOf Context triple: [Meiko Honma, causeOfReunionOf, Super Peace Busters]
-
A.
reunionWith
Indicates that two or more entities come back together after a period of separation or absence.
-
B.
reunitedIn
Indicates that entities who were previously separated have come together again at a specific time or place.
-
C.
reunitedFor
Indicates that entities who were previously separated have come back together or been brought back into association.
-
D.
reunitedAs
Indicates that entities who were previously separated have come back together or been brought back into association.
-
E.
reunionType
Indicates the specific kind or category of reunion event that relates the involved entities.
- F. None of above. chosen
Provenance (4 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: May 1, 2026, 12:09 a.m.