Triple
T7637616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoshimoto comedians |
E172918
|
entity |
| Predicate | oftenAppearOn |
P795
|
FINISHED |
| Object | national Japanese TV networks |
—
|
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: national Japanese TV networks | Statement: [Yoshimoto comedians, oftenAppearOn, national Japanese TV networks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenAppearOn Context triple: [Yoshimoto comedians, oftenAppearOn, national Japanese TV networks]
-
A.
appearsIn
chosen
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
B.
appearsFor
Indicates that one entity is presented, shown, or made visible on behalf of, or in representation of, another entity.
-
C.
bestSeenIn
Indicates that something is most effectively or appropriately experienced, observed, or appreciated within a particular context, medium, or setting.
-
D.
appearsAlongside
Indicates that two entities are present or occur together in the same context, setting, or instance.
-
E.
commonlyDepictedOn
Indicates that something is frequently shown or represented on the surface, medium, or context of another thing.
- 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fac953e08190a2f50bf783c49faf |
completed | March 27, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e8cadc8190b7977fcd213954dd |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:57 p.m.