Triple
T3378591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banana |
E71124
|
entity |
| Predicate | broadcastOrder |
P45887
|
FINISHED |
| Object | Aired alongside Cucumber and Tofu |
—
|
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: Aired alongside Cucumber and Tofu | Statement: [Banana, broadcastOrder, Aired alongside Cucumber and Tofu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastOrder Context triple: [Banana, broadcastOrder, Aired alongside Cucumber and Tofu]
-
A.
broadcastFor
Indicates that one entity transmits or disseminates content, information, or a signal on behalf of, or in service of, another entity.
-
B.
broadcastVia
Indicates that an action, message, or content is transmitted or disseminated through a specified medium, channel, or platform.
-
C.
broadcastDuring
Indicates that one event or program is broadcast while another specified time period or event is occurring.
-
D.
firstBroadcastOrder
chosen
Indicates the sequence position in which something was originally broadcast relative to other broadcasts.
-
E.
broadcastType
Indicates the specific mode or category of broadcasting used to transmit content (e.g., live, recorded, streaming, or other broadcast formats) between entities.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2eacb5c81908071a1dacc9a897a |
completed | March 8, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.