Triple
T28422160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomoyuki Sugano |
E719966
|
entity |
| Predicate | brokeWithTeam |
P122495
|
FINISHED |
| Object | Yomiuri Giants |
—
|
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: Yomiuri Giants | Statement: [Tomoyuki Sugano, brokeWithTeam, Yomiuri Giants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brokeWithTeam Context triple: [Tomoyuki Sugano, brokeWithTeam, Yomiuri Giants]
-
A.
brokeUpIn
Indicates that a romantic or close relationship between entities ended in a specified location or context.
-
B.
brokenInLeague
Indicates that an entity has performed so exceptionally within a particular league that it is considered to have "broken" or surpassed the league’s usual competitive standards or expectations.
-
C.
wasSackedBy
Indicates that one entity was dismissed or fired from a position or role by another entity.
-
D.
bondBroken
chosen
Indicates that a previously existing bond or connection between entities has been severed or is no longer intact.
-
E.
formedByBreakWith
Indicates that something came into existence as a result of a split, rupture, or separation from a prior entity or group.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:34 a.m.