Triple
T34191476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joia Rara |
E877125
|
entity |
| Predicate | hasBroadcastIn |
P27790
|
FINISHED |
| Object | international markets |
—
|
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: international markets | Statement: [Joia Rara, hasBroadcastIn, international markets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBroadcastIn Context triple: [Joia Rara, hasBroadcastIn, international markets]
-
A.
hasBroadcastStatus
Indicates the current broadcast-related state or condition of an item, such as whether it is scheduled, live, completed, or unavailable.
-
B.
wasBroadcastOn
Indicates that a media item (such as a program, episode, or event) was transmitted or aired via a particular broadcast channel, station, or network.
-
C.
hasBroadcastContent
Indicates that one entity (typically a broadcast or channel) carries, includes, or transmits the specified content.
-
D.
broadcastsIn
chosen
Indicates that one entity transmits or airs content within a particular medium, channel, location, or time frame.
-
E.
hasBroadcastHistoryWith
Indicates that two entities are connected through a record of past broadcast events involving both of them.
- 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 1, 2026, 1:55 a.m.